Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9ebc5ca199b0112977f8a7a833c72a91878439356a18d0ac64b01e4c445333d

Tx prefix hash: d5d455039761213622b00f480343f713090ea9c3e6e39bb320eb91b32397d525
Tx public key: 8ed680dc8635075af5f9f5ce7af8fa9e48139ebef76e9517cd50b1a0086af8fc
Timestamp: 1700522395 Timestamp [UCT]: 2023-11-20 23:19:55 Age [y:d:h:m:s]: 01:060:12:05:00
Block: 896072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304607 RingCT/type: yes/0
Extra: 018ed680dc8635075af5f9f5ce7af8fa9e48139ebef76e9517cd50b1a0086af8fc02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.659085073000 dcy

stealth address amount amount idx
00: 38a2ae6b585ca19c08e46bb9b4a8e2376dea23306b5053307e942df1cd254891 0.659085073000 1352323 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": 896082, "vin": [ { "gen": { "height": 896072 } } ], "vout": [ { "amount": 659085073, "target": { "key": "38a2ae6b585ca19c08e46bb9b4a8e2376dea23306b5053307e942df1cd254891" } } ], "extra": [ 1, 142, 214, 128, 220, 134, 53, 7, 90, 245, 249, 245, 206, 122, 248, 250, 158, 72, 19, 158, 190, 247, 110, 149, 23, 205, 80, 177, 160, 8, 106, 248, 252, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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