Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e5ba1dd49cc951e0831203b7cfc27df8e242eef7fbde2c89817596e754456d6

Tx prefix hash: 5a5f4e6fa9ef6de2e7c7cf016f7a3a2875a7410bafe651bbf5cb3fc4bd6be1cf
Tx public key: 6db8f092026e1cfbce6e7be7ef5cf776ec4ba95885dbd962312dad7045f4a9ec
Timestamp: 1752816935 Timestamp [UCT]: 2025-07-18 05:35:35 Age [y:d:h:m:s]: 00:174:03:18:54
Block: 1327910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123315 RingCT/type: yes/0
Extra: 016db8f092026e1cfbce6e7be7ef5cf776ec4ba95885dbd962312dad7045f4a9ec021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d7490504a0c816229ec7c4233a3e7234a6272623e34c138e3a6ad944b830933 0.600000000000 1815669 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": 1327920, "vin": [ { "gen": { "height": 1327910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d7490504a0c816229ec7c4233a3e7234a6272623e34c138e3a6ad944b830933" } } ], "extra": [ 1, 109, 184, 240, 146, 2, 110, 28, 251, 206, 110, 123, 231, 239, 92, 247, 118, 236, 75, 169, 88, 133, 219, 217, 98, 49, 45, 173, 112, 69, 244, 169, 236, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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