Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c8370c033ea7982b26225a94d274addc58df67ef6536c4857781ce7044c6acb

Tx prefix hash: 5c2643f05c362dedda98fa024668551e9e212b1b8941c9e9015ee601fefdbe19
Tx public key: adfe49e7d9b855510838c850bc4a717e92bc8c8d14e8ed4e147c51cf2384e970
Timestamp: 1696145041 Timestamp [UCT]: 2023-10-01 07:24:01 Age [y:d:h:m:s]: 02:034:20:33:54
Block: 859989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 544543 RingCT/type: yes/0
Extra: 01adfe49e7d9b855510838c850bc4a717e92bc8c8d14e8ed4e147c51cf2384e97002110000000633af99f4000000000000000000

1 output(s) for total of 0.867959551000 dcy

stealth address amount amount idx
00: 9f56e8505b1038e5fc5ff39fef3e364794c1452f5bae651a13d1f88305a24f21 0.867959551000 1314245 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": 859999, "vin": [ { "gen": { "height": 859989 } } ], "vout": [ { "amount": 867959551, "target": { "key": "9f56e8505b1038e5fc5ff39fef3e364794c1452f5bae651a13d1f88305a24f21" } } ], "extra": [ 1, 173, 254, 73, 231, 217, 184, 85, 81, 8, 56, 200, 80, 188, 74, 113, 126, 146, 188, 140, 141, 20, 232, 237, 78, 20, 124, 81, 207, 35, 132, 233, 112, 2, 17, 0, 0, 0, 6, 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