Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42bee3a34c6e19524e2a8994b8c660a9ae5d82b94fc2caca61a0bbf2930406e1

Tx prefix hash: 07985c782097341da5c92d7e26319f2c95a227360dc12dcf24426824169dde9b
Tx public key: d6e34c091923b7480f6077741cb1fec3f9fa50965b01fec332e5000c0e8cb586
Timestamp: 1709298863 Timestamp [UCT]: 2024-03-01 13:14:23 Age [y:d:h:m:s]: 01:096:02:52:47
Block: 968842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329763 RingCT/type: yes/0
Extra: 01d6e34c091923b7480f6077741cb1fec3f9fa50965b01fec332e5000c0e8cb5860211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b401bee0ffc27d3ccd17eaf080b80a7bf66f26ea88f56beaa4aa1667aa6f775 0.600000000000 1428665 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": 968852, "vin": [ { "gen": { "height": 968842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b401bee0ffc27d3ccd17eaf080b80a7bf66f26ea88f56beaa4aa1667aa6f775" } } ], "extra": [ 1, 214, 227, 76, 9, 25, 35, 183, 72, 15, 96, 119, 116, 28, 177, 254, 195, 249, 250, 80, 150, 91, 1, 254, 195, 50, 229, 0, 12, 14, 140, 181, 134, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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