Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39bd6c87bb57af754430575c72f5623dc3db7d24ed5ff4c4853aaee05a9a390c

Tx prefix hash: e85c927bfc8fad48356bd8ef7ef4597488c3b0441689d42610d313fa64f21ce7
Tx public key: a0be87d8da0e2583046ad1de7aae924afbd2c93ced7839642dbb67d9f8f70c5d
Timestamp: 1709990115 Timestamp [UCT]: 2024-03-09 13:15:15 Age [y:d:h:m:s]: 01:005:02:45:13
Block: 974573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264657 RingCT/type: yes/0
Extra: 01a0be87d8da0e2583046ad1de7aae924afbd2c93ced7839642dbb67d9f8f70c5d0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c24fc02a0f5e9946a561a846f1798f26ead3c8466549bfe77a9b3bacccc98a81 0.600000000000 1434532 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": 974583, "vin": [ { "gen": { "height": 974573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c24fc02a0f5e9946a561a846f1798f26ead3c8466549bfe77a9b3bacccc98a81" } } ], "extra": [ 1, 160, 190, 135, 216, 218, 14, 37, 131, 4, 106, 209, 222, 122, 174, 146, 74, 251, 210, 201, 60, 237, 120, 57, 100, 45, 187, 103, 217, 248, 247, 12, 93, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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