🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 8a37afbb49b8a3aadcd7d205c631dc5502017b152d7f0432e10cd41523a4e62f

Tx prefix hash: 97dec558bd438a6a5f094c533fa753d77b20e3f8921ba9524848b5e6b69b5fcd
Tx public key: b10d9ba7ad17ef2821f3d47d1eba5e699254f810e8a3429502cec70c06bf6d0e
Timestamp: 1773551471 Timestamp [UTC]: 2026-03-15 05:11:11 Age [y:d:h:m:s]: 00:001:08:26:56
Block: 1530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 976 RingCT/type: yes/0
Extra: 01b10d9ba7ad17ef2821f3d47d1eba5e699254f810e8a3429502cec70c06bf6d0e021100000002fd8f4d87000000000000000000

1 output(s) for total of 16.617533274371 nia

stealth address amount amount idx tag
00: 5c6de1949201855bf0bcf6c171508001aeeb2e4a8da44cc43a794ca62c8c31e4 16.617533274371 2618 of 0 <bb>

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": 1560, "vin": [ { "gen": { "height": 1530 } } ], "vout": [ { "amount": 16617533274371, "target": { "tagged_key": { "key": "5c6de1949201855bf0bcf6c171508001aeeb2e4a8da44cc43a794ca62c8c31e4", "view_tag": "bb" } } } ], "extra": [ 1, 177, 13, 155, 167, 173, 23, 239, 40, 33, 243, 212, 125, 30, 186, 94, 105, 146, 84, 248, 16, 232, 163, 66, 149, 2, 206, 199, 12, 6, 191, 109, 14, 2, 17, 0, 0, 0, 2, 253, 143, 77, 135, 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