🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: ba713c44aa7d8b4ca3ce942a8da51c604415d94e7a81ea08388eabb30dd5a4f9

Tx prefix hash: 7a319409b490db7ee0782ec6ddbb7ac70440ec7e368d83bac0af0e54399bdb3a
Tx public key: 440dc7e8022c459b544fe47440efe046ee1d8eb3e7348be03dcd0d740a1bd8e3
Timestamp: 1774203725 Timestamp [UTC]: 2026-03-22 18:22:05 Age [y:d:h:m:s]: 00:002:12:25:07
Block: 6084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 129 RingCT/type: yes/0
Extra: 01440dc7e8022c459b544fe47440efe046ee1d8eb3e7348be03dcd0d740a1bd8e302110000000277b3f9a2000000000000000000

1 output(s) for total of 16.539031380780 nia

stealth address amount amount idx tag
00: 023167923a5ea8c4e0785e1160d6f0dce1330a4c9b40ee6b1ce49f3e77bd8040 16.539031380780 9144 of 0 <1a>

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": 6114, "vin": [ { "gen": { "height": 6084 } } ], "vout": [ { "amount": 16539031380780, "target": { "tagged_key": { "key": "023167923a5ea8c4e0785e1160d6f0dce1330a4c9b40ee6b1ce49f3e77bd8040", "view_tag": "1a" } } } ], "extra": [ 1, 68, 13, 199, 232, 2, 44, 69, 155, 84, 79, 228, 116, 64, 239, 224, 70, 238, 29, 142, 179, 231, 52, 139, 224, 61, 205, 13, 116, 10, 27, 216, 227, 2, 17, 0, 0, 0, 2, 119, 179, 249, 162, 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