Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7bf692b19d4f6f5324cfd37ad4e1c4626158951df7a9e022e746c458a031d0c

Tx prefix hash: 997594cfd519e7f40a82db2fc345030b6309a0017e930b0a456ac495e16a616d
Tx public key: 5b20847313fb3638d7b9b45a616fdac42f9ed2790799a4e92f39a06d286a42f9
Timestamp: 1585550287 Timestamp [UCT]: 2020-03-30 06:38:07 Age [y:d:h:m:s]: 04:095:18:35:37
Block: 89822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 967472 RingCT/type: yes/0
Extra: 015b20847313fb3638d7b9b45a616fdac42f9ed2790799a4e92f39a06d286a42f902110000000137fb5df4000000000000000000

1 output(s) for total of 309.302337890000 dcy

stealth address amount amount idx
00: 9ea773063ac24303c1b8bb97d6285234e114dd2335a00d4076bf313820e31c3e 309.302337890000 160996 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": 89832, "vin": [ { "gen": { "height": 89822 } } ], "vout": [ { "amount": 309302337890, "target": { "key": "9ea773063ac24303c1b8bb97d6285234e114dd2335a00d4076bf313820e31c3e" } } ], "extra": [ 1, 91, 32, 132, 115, 19, 251, 54, 56, 215, 185, 180, 90, 97, 111, 218, 196, 47, 158, 210, 121, 7, 153, 164, 233, 47, 57, 160, 109, 40, 106, 66, 249, 2, 17, 0, 0, 0, 1, 55, 251, 93, 244, 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