Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a535f0a3b3eba9e959c053b83d1a266cbc07972b48ef0036d5696b351a261d24

Tx prefix hash: 5169811e913bb899d5425a3323eaf2c520f50036fe7b630a5c41529a38637b09
Tx public key: 68e682c761f527caab82e955b744f0e4790650d37f9dcc98615f31ae14fda5cb
Timestamp: 1703064896 Timestamp [UCT]: 2023-12-20 09:34:56 Age [y:d:h:m:s]: 01:149:16:03:33
Block: 917154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368127 RingCT/type: yes/0
Extra: 0168e682c761f527caab82e955b744f0e4790650d37f9dcc98615f31ae14fda5cb021100000002e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba8cea352e840a31d8f05c8dba117072471003fcb53b85fb2714991a45ca612d 0.600000000000 1374722 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": 917164, "vin": [ { "gen": { "height": 917154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba8cea352e840a31d8f05c8dba117072471003fcb53b85fb2714991a45ca612d" } } ], "extra": [ 1, 104, 230, 130, 199, 97, 245, 39, 202, 171, 130, 233, 85, 183, 68, 240, 228, 121, 6, 80, 211, 127, 157, 204, 152, 97, 95, 49, 174, 20, 253, 165, 203, 2, 17, 0, 0, 0, 2, 228, 187, 107, 131, 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