Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec46ad2022c4652e39145907b3bd673da07fe7f6c17485891d19703d4dae8f3e

Tx prefix hash: 51e398d8965d4f296bb6575bf00ad2160da23ab2aad78b3d613d33e5c0830e6d
Tx public key: e9b4289f7c7002f28a1408b9b955f7030a91771853cb49dfd3896dc86d500807
Timestamp: 1756266288 Timestamp [UCT]: 2025-08-27 03:44:48 Age [y:d:h:m:s]: 00:092:07:45:52
Block: 1355299 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65927 RingCT/type: yes/0
Extra: 01e9b4289f7c7002f28a1408b9b955f7030a91771853cb49dfd3896dc86d5008070211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af12525e89f30dae02e903a32f9f46df1bee2d680b6259d3e7ec26a9ea5f57f7 0.600000000000 1843298 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": 1355309, "vin": [ { "gen": { "height": 1355299 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af12525e89f30dae02e903a32f9f46df1bee2d680b6259d3e7ec26a9ea5f57f7" } } ], "extra": [ 1, 233, 180, 40, 159, 124, 112, 2, 242, 138, 20, 8, 185, 185, 85, 247, 3, 10, 145, 119, 24, 83, 203, 73, 223, 211, 137, 109, 200, 109, 80, 8, 7, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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