Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e357be432330ccbefa44df486efdb3b13e931b20add15261fd85c65daadc4b67

Tx prefix hash: f3f025dedd4ca2b95c59b147e60da94b9f401fb6546ef3d551e22d4c70711fce
Tx public key: b2ce4e7a0ab37ad067e1ba45ae81105a04e9c01797a2c23c9fcacd5220aca9b2
Timestamp: 1752318643 Timestamp [UCT]: 2025-07-12 11:10:43 Age [y:d:h:m:s]: 00:132:01:17:44
Block: 1323872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93071 RingCT/type: yes/0
Extra: 01b2ce4e7a0ab37ad067e1ba45ae81105a04e9c01797a2c23c9fcacd5220aca9b202110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65195bb770e28cd97e6cea306a7b7c92837d8483fe62bb0640e5aac8a7a794e3 0.600000000000 1811613 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": 1323882, "vin": [ { "gen": { "height": 1323872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65195bb770e28cd97e6cea306a7b7c92837d8483fe62bb0640e5aac8a7a794e3" } } ], "extra": [ 1, 178, 206, 78, 122, 10, 179, 122, 208, 103, 225, 186, 69, 174, 129, 16, 90, 4, 233, 192, 23, 151, 162, 194, 60, 159, 202, 205, 82, 32, 172, 169, 178, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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