Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e6b417c0b9e768c759e14851b2368da1d52db9a361298e8058d53417044aaed

Tx prefix hash: fd76ba657a033253263b71b4f0dbd4bfaf78dd2c3631209bc7f930f464b938cd
Tx public key: 6ee7b52b84d4ec7b1623393bdd801cd13a7cfc73309540ef958e0ba6e713f169
Timestamp: 1707443489 Timestamp [UCT]: 2024-02-09 01:51:29 Age [y:d:h:m:s]: 01:115:13:04:49
Block: 953446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343684 RingCT/type: yes/0
Extra: 016ee7b52b84d4ec7b1623393bdd801cd13a7cfc73309540ef958e0ba6e713f169021100000004c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da0f22062bdcf1a98e060c741db74054113b8f026b8fece063c5bf91382a9c9d 0.600000000000 1412654 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": 953456, "vin": [ { "gen": { "height": 953446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da0f22062bdcf1a98e060c741db74054113b8f026b8fece063c5bf91382a9c9d" } } ], "extra": [ 1, 110, 231, 181, 43, 132, 212, 236, 123, 22, 35, 57, 59, 221, 128, 28, 209, 58, 124, 252, 115, 48, 149, 64, 239, 149, 142, 11, 166, 231, 19, 241, 105, 2, 17, 0, 0, 0, 4, 197, 69, 41, 96, 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