Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 471d8e111270d915f849ee98ebe01d318949e7f5f284ab81c7daecf11e7d8b99

Tx prefix hash: d4cf7d47f3149b980bf0f9a1ca9a382911c0c57d81d0314d97cdbdbeca8657b1
Tx public key: 6dc8a8ccc74cdc9b0e31c0a16131c0d4976fe44de5de1dde8c57ff353383844e
Timestamp: 1763944748 Timestamp [UCT]: 2025-11-24 00:39:08 Age [y:d:h:m:s]: 00:003:09:36:31
Block: 1418754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2434 RingCT/type: yes/0
Extra: 016dc8a8ccc74cdc9b0e31c0a16131c0d4976fe44de5de1dde8c57ff353383844e0211000000018ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a617b61824247bd5e30cbd4a658a6111acbb8ca101ed1c4cd42128055e6e3cfb 0.600000000000 1907287 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 dinasty-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": 1418764, "vin": [ { "gen": { "height": 1418754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a617b61824247bd5e30cbd4a658a6111acbb8ca101ed1c4cd42128055e6e3cfb" } } ], "extra": [ 1, 109, 200, 168, 204, 199, 76, 220, 155, 14, 49, 192, 161, 97, 49, 192, 212, 151, 111, 228, 77, 229, 222, 29, 222, 140, 87, 255, 53, 51, 131, 132, 78, 2, 17, 0, 0, 0, 1, 140, 235, 127, 9, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8