Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dad3dd3addbf986c13f2ff5557a17bd4f9b73273ddea855434c0c97e88546a4d

Tx prefix hash: 539557a89749b8ed163a1e6d2a545fa76b8cac7316ca6c6086c67f6bff350b08
Tx public key: b08ffc74bce637b294d0e834d2fb075b6f8319e0d07c61c3dd88b4ba9b5021c8
Timestamp: 1702844090 Timestamp [UCT]: 2023-12-17 20:14:50 Age [y:d:h:m:s]: 01:324:21:53:50
Block: 915322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 491053 RingCT/type: yes/0
Extra: 01b08ffc74bce637b294d0e834d2fb075b6f8319e0d07c61c3dd88b4ba9b5021c802110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e424d0ed954a6af9d10326006326f1f0dc053be273b9cd4e9a5d93726c5d6d1a 0.600000000000 1372716 of 15

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": 915332, "vin": [ { "gen": { "height": 915322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e424d0ed954a6af9d10326006326f1f0dc053be273b9cd4e9a5d93726c5d6d1a" } } ], "extra": [ 1, 176, 143, 252, 116, 188, 230, 55, 178, 148, 208, 232, 52, 210, 251, 7, 91, 111, 131, 25, 224, 208, 124, 97, 195, 221, 136, 180, 186, 155, 80, 33, 200, 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