Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d83bae7af7605d2fb5accef36e3ea73d64aa44527ed4f2981043a8b6083d6ca

Tx prefix hash: bb3367bafdc5538167bf3409b6ba2030da0b6d1af8e302992aa678b96f208b51
Tx public key: ddd68f571ede7ace6687079a3226cb845c3779339353a4ea2d470d389dd2e8f0
Timestamp: 1593018005 Timestamp [UCT]: 2020-06-24 17:00:05 Age [y:d:h:m:s]: 04:296:23:23:30
Block: 110508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152315 RingCT/type: yes/0
Extra: 01ddd68f571ede7ace6687079a3226cb845c3779339353a4ea2d470d389dd2e8f002110000000d46a11e8a000000000000000000

1 output(s) for total of 264.144680627000 dcy

stealth address amount amount idx
00: 888545f81ba8c0e1216e6982023e8f9d03c539f05ca17582bf4359fe8319499d 264.144680627000 191394 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": 110518, "vin": [ { "gen": { "height": 110508 } } ], "vout": [ { "amount": 264144680627, "target": { "key": "888545f81ba8c0e1216e6982023e8f9d03c539f05ca17582bf4359fe8319499d" } } ], "extra": [ 1, 221, 214, 143, 87, 30, 222, 122, 206, 102, 135, 7, 154, 50, 38, 203, 132, 92, 55, 121, 51, 147, 83, 164, 234, 45, 71, 13, 56, 157, 210, 232, 240, 2, 17, 0, 0, 0, 13, 70, 161, 30, 138, 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