Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f67f10de1302260e1a9c6fe5e6dc638fec21609f1baa85f654222e24e4c2ba03

Tx prefix hash: 93d5e0f19aa8b21bfc38d50f2dc9694d7d1e69187b4272d7226a3ca9c62d4304
Tx public key: 0484dfc706b5ab66820d68ad1c11237813a311ee570f0133fcc1685377aad025
Timestamp: 1735863349 Timestamp [UCT]: 2025-01-03 00:15:49 Age [y:d:h:m:s]: 00:096:16:24:56
Block: 1188940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68884 RingCT/type: yes/0
Extra: 010484dfc706b5ab66820d68ad1c11237813a311ee570f0133fcc1685377aad025021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e67cab13f3c5e587763a143c6f69c4ae9f668b3c50294d0e1659bd072e3d1a0b 0.600000000000 1675445 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": 1188950, "vin": [ { "gen": { "height": 1188940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e67cab13f3c5e587763a143c6f69c4ae9f668b3c50294d0e1659bd072e3d1a0b" } } ], "extra": [ 1, 4, 132, 223, 199, 6, 181, 171, 102, 130, 13, 104, 173, 28, 17, 35, 120, 19, 163, 17, 238, 87, 15, 1, 51, 252, 193, 104, 83, 119, 170, 208, 37, 2, 17, 0, 0, 0, 1, 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