Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e659025dcde40591c5a8c9e9576ee3fcc41fe8d66f5cdbe5d54dee5cdd1f95f

Tx prefix hash: 2234a8bedaf6520d08e3492077d5af47389705715322f45d43a2c78e47c4e71e
Tx public key: 8ce376d02e64fae11fe714650dfebef639c027b2369ba5287dcf9c5f9924f6d7
Timestamp: 1734202016 Timestamp [UCT]: 2024-12-14 18:46:56 Age [y:d:h:m:s]: 00:025:07:48:45
Block: 1175206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18099 RingCT/type: yes/0
Extra: 018ce376d02e64fae11fe714650dfebef639c027b2369ba5287dcf9c5f9924f6d7021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ef6f2652944a199a38a4c09b6b3f5823a72f231f1395b733065643d85ca5955 0.600000000000 1661453 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": 1175216, "vin": [ { "gen": { "height": 1175206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ef6f2652944a199a38a4c09b6b3f5823a72f231f1395b733065643d85ca5955" } } ], "extra": [ 1, 140, 227, 118, 208, 46, 100, 250, 225, 31, 231, 20, 101, 13, 254, 190, 246, 57, 192, 39, 178, 54, 155, 165, 40, 125, 207, 156, 95, 153, 36, 246, 215, 2, 17, 0, 0, 0, 5, 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