Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac00690f129e82916baf1c545978af20485b7cfc136a1383c51ad25c23a62377

Tx prefix hash: adc920a00ea43aca07222f96d8c72ccb143928d41759343f081a9bcb40f858dc
Tx public key: db7aec12febd28fdeafcf70284b4b21a3d22ed8bd6f441ba18b9f71d3c0e0e1e
Timestamp: 1756332539 Timestamp [UCT]: 2025-08-27 22:08:59 Age [y:d:h:m:s]: 00:073:18:24:58
Block: 1355847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52645 RingCT/type: yes/0
Extra: 01db7aec12febd28fdeafcf70284b4b21a3d22ed8bd6f441ba18b9f71d3c0e0e1e0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c3f6e69c439a20b8eabffdf430e488fdc0c5a4580402b83d842eaf4cdc10742 0.600000000000 1843850 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": 1355857, "vin": [ { "gen": { "height": 1355847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c3f6e69c439a20b8eabffdf430e488fdc0c5a4580402b83d842eaf4cdc10742" } } ], "extra": [ 1, 219, 122, 236, 18, 254, 189, 40, 253, 234, 252, 247, 2, 132, 180, 178, 26, 61, 34, 237, 139, 214, 244, 65, 186, 24, 185, 247, 29, 60, 14, 14, 30, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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