Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63796d246ec61433733b45d3d8916fdfaad0c8b9ad078af242e662c653a25dab

Tx prefix hash: 0274a13717e9efcdff406c339b559d1584e09dfdd86b38c1bd2ef0c56cb4ad20
Tx public key: 5e94ae830d4a27fb52d918033a557b6216a2fd57dd678e304df160c91bababa8
Timestamp: 1732452654 Timestamp [UCT]: 2024-11-24 12:50:54 Age [y:d:h:m:s]: 01:068:16:13:22
Block: 1160696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307409 RingCT/type: yes/0
Extra: 015e94ae830d4a27fb52d918033a557b6216a2fd57dd678e304df160c91bababa80211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52a9fbcacaa1119e4ed48e4a1af63e42dc82838e94b562d4fe6e8a89ede11f0f 0.600000000000 1646345 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": 1160706, "vin": [ { "gen": { "height": 1160696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52a9fbcacaa1119e4ed48e4a1af63e42dc82838e94b562d4fe6e8a89ede11f0f" } } ], "extra": [ 1, 94, 148, 174, 131, 13, 74, 39, 251, 82, 217, 24, 3, 58, 85, 123, 98, 22, 162, 253, 87, 221, 103, 142, 48, 77, 241, 96, 201, 27, 171, 171, 168, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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