Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efd3286e73ad1a15272bfab7ba0a706d62a5b8202a6ac5efe4c3ddef3e1fa770

Tx prefix hash: 6f47549bf2298aa8625a4f486cf173664f9cb7ec630f6c023be26db3df1d0eae
Tx public key: cba8de34540ef65d85b96d7797095466f61d8fd15ebfac16e3e4c2cd3b48fda6
Timestamp: 1758562465 Timestamp [UCT]: 2025-09-22 17:34:25 Age [y:d:h:m:s]: 00:056:04:33:43
Block: 1374149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40226 RingCT/type: yes/0
Extra: 01cba8de34540ef65d85b96d7797095466f61d8fd15ebfac16e3e4c2cd3b48fda6021100000005b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fdc32a8c6ece0d6b3bd44b1944433dd620750d7661384eeb464b0a4878620de 0.600000000000 1862234 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": 1374159, "vin": [ { "gen": { "height": 1374149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fdc32a8c6ece0d6b3bd44b1944433dd620750d7661384eeb464b0a4878620de" } } ], "extra": [ 1, 203, 168, 222, 52, 84, 14, 246, 93, 133, 185, 109, 119, 151, 9, 84, 102, 246, 29, 143, 209, 94, 191, 172, 22, 227, 228, 194, 205, 59, 72, 253, 166, 2, 17, 0, 0, 0, 5, 178, 247, 132, 196, 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