Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b238c96434ba1ae693c31fa9822be4a86c3337e2b9e7b4ba6af462b7d0571c02

Tx prefix hash: 0cde6e2f9cf81657b9f3f94393d687d6a3b72255af58c48beb8d15b14d1431cd
Tx public key: 87267a15c756869712444241dad923a57e8e68dce6aaefb9da701e8688b023c1
Timestamp: 1759284464 Timestamp [UCT]: 2025-10-01 02:07:44 Age [y:d:h:m:s]: 00:123:16:56:59
Block: 1380121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88408 RingCT/type: yes/0
Extra: 0187267a15c756869712444241dad923a57e8e68dce6aaefb9da701e8688b023c1021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb7b287a93eb07bfdfa57cea73a8e614a5268869316a1aa5dbad4e1b9ab163c6 0.600000000000 1868232 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": 1380131, "vin": [ { "gen": { "height": 1380121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb7b287a93eb07bfdfa57cea73a8e614a5268869316a1aa5dbad4e1b9ab163c6" } } ], "extra": [ 1, 135, 38, 122, 21, 199, 86, 134, 151, 18, 68, 66, 65, 218, 217, 35, 165, 126, 142, 104, 220, 230, 170, 239, 185, 218, 112, 30, 134, 136, 176, 35, 193, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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