Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e3f92b7da5f289daec59ebe7732032376e3d1b855aa720e812af7963663a954

Tx prefix hash: 1a4da25ea938ecf3f8c6fe1d7ac490e5bdb725618f60697509239193ea5baf8a
Tx public key: af9a3c9ec170deb86468e51dc704d013dc7a8856c221cfc9b7e384576313b5f4
Timestamp: 1699732526 Timestamp [UCT]: 2023-11-11 19:55:26 Age [y:d:h:m:s]: 01:151:07:27:48
Block: 889534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369331 RingCT/type: yes/0
Extra: 01af9a3c9ec170deb86468e51dc704d013dc7a8856c221cfc9b7e384576313b5f402110000000433af99f4000000000000000000

1 output(s) for total of 0.692794759000 dcy

stealth address amount amount idx
00: d47b242cda68d64dc569d43f96f29fd3e335b7e3eb2bc515c462479c2e9c6895 0.692794759000 1345537 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": 889544, "vin": [ { "gen": { "height": 889534 } } ], "vout": [ { "amount": 692794759, "target": { "key": "d47b242cda68d64dc569d43f96f29fd3e335b7e3eb2bc515c462479c2e9c6895" } } ], "extra": [ 1, 175, 154, 60, 158, 193, 112, 222, 184, 100, 104, 229, 29, 199, 4, 208, 19, 220, 122, 136, 86, 194, 33, 207, 201, 183, 227, 132, 87, 99, 19, 181, 244, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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