Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 171b91b8f6adf5d1076aa22bdee1fb2285547290d57967a58568cdf035cdffa7

Tx prefix hash: 5f5738caaf2e61f0e7ff5f3561cad04fa43d3d029cf9e9d1278fd70291a2e1c6
Tx public key: 84ddde16ea50b25b28e9c5180355e6bad1aadceb77fd050b0f9648e58af350b2
Timestamp: 1753835106 Timestamp [UCT]: 2025-07-30 00:25:06 Age [y:d:h:m:s]: 00:164:19:16:47
Block: 1336291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116696 RingCT/type: yes/0
Extra: 0184ddde16ea50b25b28e9c5180355e6bad1aadceb77fd050b0f9648e58af350b2021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f25a4a57f4f998c860afe362e31e478dc3a5ef9ef97352fc5b7105b8e40b230 0.600000000000 1824092 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": 1336301, "vin": [ { "gen": { "height": 1336291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f25a4a57f4f998c860afe362e31e478dc3a5ef9ef97352fc5b7105b8e40b230" } } ], "extra": [ 1, 132, 221, 222, 22, 234, 80, 178, 91, 40, 233, 197, 24, 3, 85, 230, 186, 209, 170, 220, 235, 119, 253, 5, 11, 15, 150, 72, 229, 138, 243, 80, 178, 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