Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 986b47897b2c31ff476e5b97c4bf9ac1700ef4027a99c6f16dc58099edcf457a

Tx prefix hash: cb533054d7811d960326960bbf37ebfe67d1d3c13c580dc6a282adb0cbe1def3
Tx public key: 2f32287243b11dd327518776f8fece47d3620915b4717cf937752dcaaafa84a7
Timestamp: 1581090614 Timestamp [UCT]: 2020-02-07 15:50:14 Age [y:d:h:m:s]: 04:324:23:31:14
Block: 60659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123713 RingCT/type: yes/0
Extra: 012f32287243b11dd327518776f8fece47d3620915b4717cf937752dcaaafa84a702110000000312c4732d000000000000000000

1 output(s) for total of 386.377981752000 dcy

stealth address amount amount idx
00: f4ddd142dc117358c2addc1594eba33ed2156d11d43c19a292eef78281fbd0dc 386.377981752000 111696 of 0

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": 60669, "vin": [ { "gen": { "height": 60659 } } ], "vout": [ { "amount": 386377981752, "target": { "key": "f4ddd142dc117358c2addc1594eba33ed2156d11d43c19a292eef78281fbd0dc" } } ], "extra": [ 1, 47, 50, 40, 114, 67, 177, 29, 211, 39, 81, 135, 118, 248, 254, 206, 71, 211, 98, 9, 21, 180, 113, 124, 249, 55, 117, 45, 202, 170, 250, 132, 167, 2, 17, 0, 0, 0, 3, 18, 196, 115, 45, 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