🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 22c8466ec054a720d5c8fcd0fa049c436459f39205c10d8bdbcc552dfc40ba63

Tx prefix hash: dc048776a5157dc41a853190a9f785322f7a21e5864c4f6912f652f873d69611
Tx public key: b92d5b0de35d8c9fd652f7416d6c3a95df8b0b00ead1832e60ba7961785ff126
Timestamp: 1773790325 Timestamp [UTC]: 2026-03-17 23:32:05 Age [y:d:h:m:s]: 00:003:13:46:41
Block: 3417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1189 RingCT/type: yes/0
Extra: 01b92d5b0de35d8c9fd652f7416d6c3a95df8b0b00ead1832e60ba7961785ff126021100000002774cb830000000000000000000

1 output(s) for total of 16.581151596515 nia

stealth address amount amount idx tag
00: 4ac4de2d277a66021f0f6967d7fde035e8045853aa7d2d5de726008a4effb79e 16.581151596515 5987 of 0 <fc>

Check which outputs belong to given Ninacatcoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Ninacatcoin in this transaction

Tx private key can be obtained using get_tx_key command in ninacatcoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 3447, "vin": [ { "gen": { "height": 3417 } } ], "vout": [ { "amount": 16581151596515, "target": { "tagged_key": { "key": "4ac4de2d277a66021f0f6967d7fde035e8045853aa7d2d5de726008a4effb79e", "view_tag": "fc" } } } ], "extra": [ 1, 185, 45, 91, 13, 227, 93, 140, 159, 214, 82, 247, 65, 109, 108, 58, 149, 223, 139, 11, 0, 234, 209, 131, 46, 96, 186, 121, 97, 120, 95, 241, 38, 2, 17, 0, 0, 0, 2, 119, 76, 184, 48, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): -- (1.2) | ninacatcoin version: 0.1.0.0-unknown