Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39f386f14e661fd071b9864f3580f49dc879eefb1ae7dff8849f13e65f5a6202

Tx prefix hash: 9ebe12842358b6520a5c8d4edf3e5a4ccc7f3e5c221f88c6f2aaae4ef1f4d049
Tx public key: 62a5f2328efc065eb9978bcfadf681dd2dd143329cc02e11490503077397803e
Timestamp: 1761857367 Timestamp [UCT]: 2025-10-30 20:49:27 Age [y:d:h:m:s]: 00:011:02:33:11
Block: 1401464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7939 RingCT/type: yes/0
Extra: 0162a5f2328efc065eb9978bcfadf681dd2dd143329cc02e11490503077397803e021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2027987608fd02a2d3d3fd40d95661c207b6e964dea1701dd0e715b396c4e0eb 0.600000000000 1889783 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": 1401474, "vin": [ { "gen": { "height": 1401464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2027987608fd02a2d3d3fd40d95661c207b6e964dea1701dd0e715b396c4e0eb" } } ], "extra": [ 1, 98, 165, 242, 50, 142, 252, 6, 94, 185, 151, 139, 207, 173, 246, 129, 221, 45, 209, 67, 50, 156, 192, 46, 17, 73, 5, 3, 7, 115, 151, 128, 62, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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