Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1853220e52c9701572e27a2dfd1c8de4ac4042bf4e52e3e9b63466e8da760fe0

Tx prefix hash: 9e115a695f2917d2f287373657d9f95a744e165587b9dc9674d38ba5cd514708
Tx public key: 61f35d125d315ed0b8f6788d49be6f26edfc5e9758f2c3f1bb4284fe8e97eb9d
Timestamp: 1710071912 Timestamp [UCT]: 2024-03-10 11:58:32 Age [y:d:h:m:s]: 01:271:00:58:24
Block: 975260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452446 RingCT/type: yes/0
Extra: 0161f35d125d315ed0b8f6788d49be6f26edfc5e9758f2c3f1bb4284fe8e97eb9d0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eaf7f5b7d30697cd13b901a9048636649856139c0b3a18b40da27de1c13639ba 0.600000000000 1435231 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": 975270, "vin": [ { "gen": { "height": 975260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eaf7f5b7d30697cd13b901a9048636649856139c0b3a18b40da27de1c13639ba" } } ], "extra": [ 1, 97, 243, 93, 18, 93, 49, 94, 208, 184, 246, 120, 141, 73, 190, 111, 38, 237, 252, 94, 151, 88, 242, 195, 241, 187, 66, 132, 254, 142, 151, 235, 157, 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