Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ad4a24bd09f6d0b165ce0a99b3ce5d10343b0282b507e3d83cf0cbdc8a3c477

Tx prefix hash: c526aa10e811dc8977a49fb2b4ea53975ef069ccb1a159d189ee07e97944e2d2
Tx public key: d3c8de8e962b1d10e63753e2002dbd70fd4a789a6a48132bad0577dda3cf2196
Timestamp: 1590432938 Timestamp [UCT]: 2020-05-25 18:55:38 Age [y:d:h:m:s]: 04:251:15:59:35
Block: 103255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1105771 RingCT/type: yes/0
Extra: 01d3c8de8e962b1d10e63753e2002dbd70fd4a789a6a48132bad0577dda3cf219602110000034fff0e1d7d000000000000000000

1 output(s) for total of 279.185938251000 dcy

stealth address amount amount idx
00: a4bc6408b521801fd3632e9f41fde73f90efb498d7e5d3958e2548fb1a590684 279.185938251000 181160 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": 103265, "vin": [ { "gen": { "height": 103255 } } ], "vout": [ { "amount": 279185938251, "target": { "key": "a4bc6408b521801fd3632e9f41fde73f90efb498d7e5d3958e2548fb1a590684" } } ], "extra": [ 1, 211, 200, 222, 142, 150, 43, 29, 16, 230, 55, 83, 226, 0, 45, 189, 112, 253, 74, 120, 154, 106, 72, 19, 43, 173, 5, 119, 221, 163, 207, 33, 150, 2, 17, 0, 0, 3, 79, 255, 14, 29, 125, 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