Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64fab1b4e98f7ea59c57bec7c968993765863caa8cf28fc85058108903feaec1

Tx prefix hash: 035164dafd59cc7c19f853bdb6f01d8645d6b1474a05e123c4ffc791f097042c
Tx public key: 1692d012195d851db2e3217a6aae178732ce985b67bef8bce63ec71bcccc72be
Timestamp: 1716820193 Timestamp [UCT]: 2024-05-27 14:29:53 Age [y:d:h:m:s]: 00:296:07:45:07
Block: 1031213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211783 RingCT/type: yes/0
Extra: 011692d012195d851db2e3217a6aae178732ce985b67bef8bce63ec71bcccc72be0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 017d44c7eae651ce68f7959e6847ad134c90e8c5e2df369983bb2a15fb98c32c 0.600000000000 1499604 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": 1031223, "vin": [ { "gen": { "height": 1031213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "017d44c7eae651ce68f7959e6847ad134c90e8c5e2df369983bb2a15fb98c32c" } } ], "extra": [ 1, 22, 146, 208, 18, 25, 93, 133, 29, 178, 227, 33, 122, 106, 174, 23, 135, 50, 206, 152, 91, 103, 190, 248, 188, 230, 62, 199, 27, 204, 204, 114, 190, 2, 17, 0, 0, 0, 7, 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