Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5820eac35549714f1c5dda8ea3e00c29d769be42a17428cae334600ff25294f9

Tx prefix hash: a34c48325133e3b8b0fff1ecae21caa5213be6fd4c9ab16fc716b3b3ba866e54
Tx public key: 0edd5e4fcd8df6486f961ccfbbb851122d36cac2c70e33c23c700d5edbf58f5a
Timestamp: 1737609898 Timestamp [UCT]: 2025-01-23 05:24:58 Age [y:d:h:m:s]: 00:147:00:42:39
Block: 1203355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104796 RingCT/type: yes/0
Extra: 010edd5e4fcd8df6486f961ccfbbb851122d36cac2c70e33c23c700d5edbf58f5a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a49b2abf65d0cb8e1d1cd6488ba14203bfcc60687ffe7f186041577ec880f0e6 0.600000000000 1690032 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": 1203365, "vin": [ { "gen": { "height": 1203355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a49b2abf65d0cb8e1d1cd6488ba14203bfcc60687ffe7f186041577ec880f0e6" } } ], "extra": [ 1, 14, 221, 94, 79, 205, 141, 246, 72, 111, 150, 28, 207, 187, 184, 81, 18, 45, 54, 202, 194, 199, 14, 51, 194, 60, 112, 13, 94, 219, 245, 143, 90, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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