Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82807d59ffb0595d23e65e7fc43a98da64f6796cb92339ba686d044902639514

Tx prefix hash: a6d967f0ebd17437240c6b6b9a51e90dd75c3bab8cb7fe3b744949143d60260f
Tx public key: ece6ab0ea3f415f602778d3d68decf48a1c298f6e22624ad7a2313743a5b4cce
Timestamp: 1750714234 Timestamp [UCT]: 2025-06-23 21:30:34 Age [y:d:h:m:s]: 00:150:19:49:38
Block: 1311363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105727 RingCT/type: yes/0
Extra: 01ece6ab0ea3f415f602778d3d68decf48a1c298f6e22624ad7a2313743a5b4cce021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38d9c4061623a5c94a346a81d325e9d78fbe002c378130d4fb7a778beea3916a 0.600000000000 1798990 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": 1311373, "vin": [ { "gen": { "height": 1311363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38d9c4061623a5c94a346a81d325e9d78fbe002c378130d4fb7a778beea3916a" } } ], "extra": [ 1, 236, 230, 171, 14, 163, 244, 21, 246, 2, 119, 141, 61, 104, 222, 207, 72, 161, 194, 152, 246, 226, 38, 36, 173, 122, 35, 19, 116, 58, 91, 76, 206, 2, 17, 0, 0, 0, 2, 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