Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39a2bb5c7d13c1ec83631e94f9954ea45dcb08873270764c40378282392665f4

Tx prefix hash: 9431f619f9dddeef05aba36412423c8f01c4ce0747c0c127bc3da5bea9cded1b
Tx public key: 10f9f4132e8762b9cdd390824842ee5a7a2815a45b4ac4b88c64dcfb14424a8b
Timestamp: 1755709817 Timestamp [UCT]: 2025-08-20 17:10:17 Age [y:d:h:m:s]: 00:098:20:13:53
Block: 1350719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70560 RingCT/type: yes/0
Extra: 0110f9f4132e8762b9cdd390824842ee5a7a2815a45b4ac4b88c64dcfb14424a8b021100000004d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20a592da30bfc81b3321617e7c715f92f838f1d30c631f32f21a388220bb1d97 0.600000000000 1838666 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": 1350729, "vin": [ { "gen": { "height": 1350719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20a592da30bfc81b3321617e7c715f92f838f1d30c631f32f21a388220bb1d97" } } ], "extra": [ 1, 16, 249, 244, 19, 46, 135, 98, 185, 205, 211, 144, 130, 72, 66, 238, 90, 122, 40, 21, 164, 91, 74, 196, 184, 140, 100, 220, 251, 20, 66, 74, 139, 2, 17, 0, 0, 0, 4, 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