Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8813685332a0baf1f83aa5865a03cca89a9c68dd339efd7181231791a1e0e9ba

Tx prefix hash: 4a31b6a6b931bff552c41db71c43caa28ee9bb3f3a72324540622abd166c938f
Tx public key: 667496d01a78acc6c00bbe23d88f07dfdcde875cdccde6110258a33c3a6bdef4
Timestamp: 1709111637 Timestamp [UCT]: 2024-02-28 09:13:57 Age [y:d:h:m:s]: 00:344:01:39:01
Block: 967291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246024 RingCT/type: yes/0
Extra: 01667496d01a78acc6c00bbe23d88f07dfdcde875cdccde6110258a33c3a6bdef40211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6beb5cfb9141513a6aa0141a0143f75657185aaf64c5c4ce64b872a9d251d511 0.600000000000 1427068 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": 967301, "vin": [ { "gen": { "height": 967291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6beb5cfb9141513a6aa0141a0143f75657185aaf64c5c4ce64b872a9d251d511" } } ], "extra": [ 1, 102, 116, 150, 208, 26, 120, 172, 198, 192, 11, 190, 35, 216, 143, 7, 223, 220, 222, 135, 92, 220, 205, 230, 17, 2, 88, 163, 60, 58, 107, 222, 244, 2, 17, 0, 0, 0, 6, 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