🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 0a8f15ad3384b99c2ce958fefa3a40d7a6c987b02d1a90d6920ed39dd313a132

Tx prefix hash: 9973cbefd0f5c0b9918bafed2c8929ae1ee1521aa3e9bab59c03993b50086e40
Tx public key: d7c4b1dee52dfc8959b14a3f631090d081dac72febb45d3d7356d929e222188e
Timestamp: 1773448111 Timestamp [UTC]: 2026-03-14 00:28:31 Age [y:d:h:m:s]: 00:002:09:03:19
Block: 693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1693 RingCT/type: yes/0
Extra: 01d7c4b1dee52dfc8959b14a3f631090d081dac72febb45d3d7356d929e222188e02110000000cafac54ac000000000000000000

1 output(s) for total of 16.627487083628 nia

stealth address amount amount idx tag
00: ce73778ec654152e4e5805411f8079ed7e198a7d995b09502d79c7437bdfdf2c 16.627487083628 915 of 0 <a5>

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": 723, "vin": [ { "gen": { "height": 693 } } ], "vout": [ { "amount": 16627487083628, "target": { "tagged_key": { "key": "ce73778ec654152e4e5805411f8079ed7e198a7d995b09502d79c7437bdfdf2c", "view_tag": "a5" } } } ], "extra": [ 1, 215, 196, 177, 222, 229, 45, 252, 137, 89, 177, 74, 63, 99, 16, 144, 208, 129, 218, 199, 47, 235, 180, 93, 61, 115, 86, 217, 41, 226, 34, 24, 142, 2, 17, 0, 0, 0, 12, 175, 172, 84, 172, 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