Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 365464c756ffc7c0369c72f6f5c29758d959ba976a1b00ffe2cd83362f8c9d57

Tx prefix hash: 14842a970e35827594c96ca6fbb4d9ab273c60081078f18f85dd6f5fcd4c9403
Tx public key: c820961622a325939a13e1b7ce23e3f1e68b57e6e977c0b49e397014d3549656
Timestamp: 1719517578 Timestamp [UCT]: 2024-06-27 19:46:18 Age [y:d:h:m:s]: 00:283:19:25:22
Block: 1053547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202803 RingCT/type: yes/0
Extra: 01c820961622a325939a13e1b7ce23e3f1e68b57e6e977c0b49e397014d35496560211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8fbff91d29cf45cbbab332834d4c7f40e5640ef2c62323f3efad82ed51f1291d 0.600000000000 1523894 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": 1053557, "vin": [ { "gen": { "height": 1053547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fbff91d29cf45cbbab332834d4c7f40e5640ef2c62323f3efad82ed51f1291d" } } ], "extra": [ 1, 200, 32, 150, 22, 34, 163, 37, 147, 154, 19, 225, 183, 206, 35, 227, 241, 230, 139, 87, 230, 233, 119, 192, 180, 158, 57, 112, 20, 211, 84, 150, 86, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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