Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 389c2517de0b7ca4b36ebdcfdc7f586d79b786c28e8c515338e4cff7ef273787

Tx prefix hash: bb21b9a1b7dc35e7e5806562e7f5b9885bb577c4749c3b795f21f2314e5e7bde
Tx public key: 68fab45184f62acc80fa68d2c5514f49c4da24c2999dd3efe5e76715a4c45bbe
Timestamp: 1752308288 Timestamp [UCT]: 2025-07-12 08:18:08 Age [y:d:h:m:s]: 00:181:06:52:19
Block: 1323783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128342 RingCT/type: yes/0
Extra: 0168fab45184f62acc80fa68d2c5514f49c4da24c2999dd3efe5e76715a4c45bbe02110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cd5d91a0546e06debf051e8dc202bda61effd2f1b8b7b116cdfbd14b4406805 0.600000000000 1811524 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": 1323793, "vin": [ { "gen": { "height": 1323783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cd5d91a0546e06debf051e8dc202bda61effd2f1b8b7b116cdfbd14b4406805" } } ], "extra": [ 1, 104, 250, 180, 81, 132, 246, 42, 204, 128, 250, 104, 210, 197, 81, 79, 73, 196, 218, 36, 194, 153, 157, 211, 239, 229, 231, 103, 21, 164, 196, 91, 190, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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