Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67f8f12cbd42e64f1fc87667c5e1896436c29bf4fe3868a5cccd28eb8024d943

Tx prefix hash: b5e17871e5b60d80773a9216e62313ad30d7fd2e469fcb69d8d4794e22feaedf
Tx public key: 6f0f32691804f3cdbeec99597a68d91db9cbd52e1a0dc0502689c2d274292022
Timestamp: 1732953886 Timestamp [UCT]: 2024-11-30 08:04:46 Age [y:d:h:m:s]: 00:113:11:07:13
Block: 1164851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80889 RingCT/type: yes/0
Extra: 016f0f32691804f3cdbeec99597a68d91db9cbd52e1a0dc0502689c2d274292022021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a0c70b3807afc4433e8fd819e03e202225cd581b71f1545514c5d8466ea34ca 0.600000000000 1650526 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": 1164861, "vin": [ { "gen": { "height": 1164851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a0c70b3807afc4433e8fd819e03e202225cd581b71f1545514c5d8466ea34ca" } } ], "extra": [ 1, 111, 15, 50, 105, 24, 4, 243, 205, 190, 236, 153, 89, 122, 104, 217, 29, 185, 203, 213, 46, 26, 13, 192, 80, 38, 137, 194, 210, 116, 41, 32, 34, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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