Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b08a088a1d1595b593102b4b523cd25a6fef6c13114f5618a97583dc41d87584

Tx prefix hash: c42de0a6ed23b273a372412b67df9f601ab432b1691822eef7489303059b74c7
Tx public key: fc70a961f0938dd97e1d37478cd7f116f5015dd788ae259e6a2f019cfa7d8584
Timestamp: 1761916479 Timestamp [UCT]: 2025-10-31 13:14:39 Age [y:d:h:m:s]: 00:013:15:31:19
Block: 1401951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9761 RingCT/type: yes/0
Extra: 01fc70a961f0938dd97e1d37478cd7f116f5015dd788ae259e6a2f019cfa7d8584021100000003df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a03439d3918d1b2b11983e8d9186f5f82a611e6c2b81751505e387fe564f77af 0.600000000000 1890270 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": 1401961, "vin": [ { "gen": { "height": 1401951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a03439d3918d1b2b11983e8d9186f5f82a611e6c2b81751505e387fe564f77af" } } ], "extra": [ 1, 252, 112, 169, 97, 240, 147, 141, 217, 126, 29, 55, 71, 140, 215, 241, 22, 245, 1, 93, 215, 136, 174, 37, 158, 106, 47, 1, 156, 250, 125, 133, 132, 2, 17, 0, 0, 0, 3, 223, 90, 36, 122, 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