Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33c79597146af2aa7608f1db1db56cacbb42b9b8d842b704f071081a8e9fc33f

Tx prefix hash: dcd110fcef34c7ab37f7aabd6b47a5fadf81bc325eefca14565bd508b1e2fb52
Tx public key: 553319f29890da2163a33f786239c8d330160fe0b648fdc6076a37683eec0a9b
Timestamp: 1578316744 Timestamp [UCT]: 2020-01-06 13:19:04 Age [y:d:h:m:s]: 05:125:15:54:31
Block: 39689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1239970 RingCT/type: yes/0
Extra: 01553319f29890da2163a33f786239c8d330160fe0b648fdc6076a37683eec0a9b02110000010f17786bcf000000000000000000

1 output(s) for total of 453.421610499000 dcy

stealth address amount amount idx
00: 6006357d615853b1ab9121d0eac3908f66b2f469b0b96a656d4eac2745a411f0 453.421610499000 68841 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": 39699, "vin": [ { "gen": { "height": 39689 } } ], "vout": [ { "amount": 453421610499, "target": { "key": "6006357d615853b1ab9121d0eac3908f66b2f469b0b96a656d4eac2745a411f0" } } ], "extra": [ 1, 85, 51, 25, 242, 152, 144, 218, 33, 99, 163, 63, 120, 98, 57, 200, 211, 48, 22, 15, 224, 182, 72, 253, 198, 7, 106, 55, 104, 62, 236, 10, 155, 2, 17, 0, 0, 1, 15, 23, 120, 107, 207, 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