Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: cd6131c71fe1ea61bc5feeaeee20368a451c396a1d7c62c63778f9339c06d7a2

Tx prefix hash: 878eb01c2da00bddbc07e290eced6e29483537d9895a42577ce8d3c9f02adc14
Tx public key: ccd0dec09b16398bb2bf40c37e3064f8d0abc4c5633a0fdee124748b65549ef8
Timestamp: 1736396966 Timestamp [UTC]: 2025-01-09 04:29:26 Age [y:d:h:m:s]: 01:316:09:58:20
Block: 1193352 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490118 RingCT/type: yes/0
Extra: 01ccd0dec09b16398bb2bf40c37e3064f8d0abc4c5633a0fdee124748b65549ef8021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7b833ccdff0ea130a618403655bf9e6e71a3e5ceacf053795643660334e01c29 0.000600000000 1679911 of 15 -

Check which outputs belong to given dinastycoin 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 dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-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": 1193362, "vin": [ { "gen": { "height": 1193352 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b833ccdff0ea130a618403655bf9e6e71a3e5ceacf053795643660334e01c29" } } ], "extra": [ 1, 204, 208, 222, 192, 155, 22, 57, 139, 178, 191, 64, 195, 126, 48, 100, 248, 208, 171, 196, 197, 99, 58, 15, 222, 225, 36, 116, 139, 101, 84, 158, 248, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: