🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: c3c0169b6b61227ae8ef7cab05935819bbf810e8ba72be20268a1c638d750bb4

Tx prefix hash: c687b3a7feb344eab90e1bfaa880d52b06ece59eea9a7a428f258d7c7343e4cb
Tx public key: af4a60ecf11ee55cb81ed6f0497c503f439d7215e4d354bf7b4e2bc3a6e81b10
Timestamp: 1773800968 Timestamp [UTC]: 2026-03-18 02:29:28 Age [y:d:h:m:s]: 00:003:09:21:10
Block: 3500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106 RingCT/type: yes/0
Extra: 01af4a60ecf11ee55cb81ed6f0497c503f439d7215e4d354bf7b4e2bc3a6e81b10021100000007774cb830000000000000000000

1 output(s) for total of 16.579839161714 nia

stealth address amount amount idx tag
00: 04757f97737881642644af2882efaa5fb7bbe2968eab42cc5c113c937796e252 16.579839161714 6081 of 0 <57>

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": 3530, "vin": [ { "gen": { "height": 3500 } } ], "vout": [ { "amount": 16579839161714, "target": { "tagged_key": { "key": "04757f97737881642644af2882efaa5fb7bbe2968eab42cc5c113c937796e252", "view_tag": "57" } } } ], "extra": [ 1, 175, 74, 96, 236, 241, 30, 229, 92, 184, 30, 214, 240, 73, 124, 80, 63, 67, 157, 114, 21, 228, 211, 84, 191, 123, 78, 43, 195, 166, 232, 27, 16, 2, 17, 0, 0, 0, 7, 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