Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f6452ac09fa385de06b9eb34c54b6ecf2ccc3d49c98cfbc66436b0488039988

Tx prefix hash: 57b61f4db6d937680f5db6d9e5bb65f8dc36d9e9441fe6c3bdfca373ec8e2d52
Tx public key: baf526eb72f2e45a1712cfed4aecf449ba9b97d242a3af768e1778c9f682b1af
Timestamp: 1702854458 Timestamp [UCT]: 2023-12-17 23:07:38 Age [y:d:h:m:s]: 01:033:15:12:25
Block: 915409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285353 RingCT/type: yes/0
Extra: 01baf526eb72f2e45a1712cfed4aecf449ba9b97d242a3af768e1778c9f682b1af02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8bc35bd788b3ed6d88033486abdcb14c6928b60b9af293a34f53fa660178360 0.600000000000 1372805 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": 915419, "vin": [ { "gen": { "height": 915409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8bc35bd788b3ed6d88033486abdcb14c6928b60b9af293a34f53fa660178360" } } ], "extra": [ 1, 186, 245, 38, 235, 114, 242, 228, 90, 23, 18, 207, 237, 74, 236, 244, 73, 186, 155, 151, 210, 66, 163, 175, 118, 142, 23, 120, 201, 246, 130, 177, 175, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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