Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d19e1fa15055d11b9ebca4a3536fa0c831db964467334295b8316dd54a564114

Tx prefix hash: 164f0f05d58192ba3c213a5bdcbbaaf35429ed19aadc5cb2c459c576ffdda4ab
Tx public key: 8e58035d26ce9c9c06fbdbc4e8cab6c7c72c6eeb576ed059848313a030cb6960
Timestamp: 1721358482 Timestamp [UCT]: 2024-07-19 03:08:02 Age [y:d:h:m:s]: 00:219:06:37:58
Block: 1068833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156589 RingCT/type: yes/0
Extra: 018e58035d26ce9c9c06fbdbc4e8cab6c7c72c6eeb576ed059848313a030cb696002110000000291e13c04000000000000000000

1 output(s) for total of 0.615610000000 dcy

stealth address amount amount idx
00: 980062672d6b28dd9161c305d9a199e7df35f87b4fa2750ea8ab3e60da3d92c4 0.615610000000 1540014 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": 1068843, "vin": [ { "gen": { "height": 1068833 } } ], "vout": [ { "amount": 615610000, "target": { "key": "980062672d6b28dd9161c305d9a199e7df35f87b4fa2750ea8ab3e60da3d92c4" } } ], "extra": [ 1, 142, 88, 3, 93, 38, 206, 156, 156, 6, 251, 219, 196, 232, 202, 182, 199, 199, 44, 110, 235, 87, 110, 208, 89, 132, 131, 19, 160, 48, 203, 105, 96, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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