Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6d9a3e7c6ccf47f99b78d0fe835e6931f4237e94c64889c3134020dec2b92a2

Tx prefix hash: 7567f02bbd3b990459488e71edde44b31eed81307dd425a1e305b05804203b1b
Tx public key: 16339b653a93cd5ee20354bce1b3205af5c040551cae74a3d3948e5982f6c083
Timestamp: 1761159239 Timestamp [UTC]: 2025-10-22 18:53:59 Age [y:d:h:m:s]: 01:030:19:48:08
Block: 1395675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287819 RingCT/type: yes/0
Extra: 0116339b653a93cd5ee20354bce1b3205af5c040551cae74a3d3948e5982f6c0830211000000085dfbbe2a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 689daf13e50734af514d84c3f87c2df5939a73c0478383dbf2951bc4a9914d3d 0.000600000000 1883958 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": 1395685, "vin": [ { "gen": { "height": 1395675 } } ], "vout": [ { "amount": 600000000, "target": { "key": "689daf13e50734af514d84c3f87c2df5939a73c0478383dbf2951bc4a9914d3d" } } ], "extra": [ 1, 22, 51, 155, 101, 58, 147, 205, 94, 226, 3, 84, 188, 225, 179, 32, 90, 245, 192, 64, 85, 28, 174, 116, 163, 211, 148, 142, 89, 130, 246, 192, 131, 2, 17, 0, 0, 0, 8, 93, 251, 190, 42, 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: