Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93efb3de00879c41a4d9f25f8f5315902ece1e41449400fbe7eca717ea98967d

Tx prefix hash: bf0eca0236cfe3304f1057d88d1a728c49df2ea3207dcdf9a268e271f3f8c5e8
Tx public key: 58dee9b4d7f02be091669febfb32fc620037462d9d01df975ca2e06b2547961c
Timestamp: 1701154573 Timestamp [UCT]: 2023-11-28 06:56:13 Age [y:d:h:m:s]: 01:340:01:21:22
Block: 901313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501912 RingCT/type: yes/0
Extra: 0158dee9b4d7f02be091669febfb32fc620037462d9d01df975ca2e06b2547961c0211000000024b8f5122000000000000000000

1 output(s) for total of 0.633250964000 dcy

stealth address amount amount idx
00: 651f44165b1667bcb1ec0019ad73abbcca06773aebdbd106d5010622f9e15cfc 0.633250964000 1357862 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": 901323, "vin": [ { "gen": { "height": 901313 } } ], "vout": [ { "amount": 633250964, "target": { "key": "651f44165b1667bcb1ec0019ad73abbcca06773aebdbd106d5010622f9e15cfc" } } ], "extra": [ 1, 88, 222, 233, 180, 215, 240, 43, 224, 145, 102, 159, 235, 251, 50, 252, 98, 0, 55, 70, 45, 157, 1, 223, 151, 92, 162, 224, 107, 37, 71, 150, 28, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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