Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e10350d64f723fcb6b86dfd9b3e095e4c015f11420e5c327b27bad2094a5479

Tx prefix hash: b64acd3931286472f239c91e2ec5a21ca9f844dac87af7e22c76017aee4395a0
Tx public key: e3bc20b6af66ce33d2372debeb1a6f91453b7fe9535b61c028af15bfd2f9d94b
Timestamp: 1761342829 Timestamp [UCT]: 2025-10-24 21:53:49 Age [y:d:h:m:s]: 00:034:09:30:37
Block: 1397200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24614 RingCT/type: yes/0
Extra: 01e3bc20b6af66ce33d2372debeb1a6f91453b7fe9535b61c028af15bfd2f9d94b0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8696a9b1c141d032e21cc4692ffd7201e4494a3e69613f027e634520e1a6d49f 0.600000000000 1885491 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": 1397210, "vin": [ { "gen": { "height": 1397200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8696a9b1c141d032e21cc4692ffd7201e4494a3e69613f027e634520e1a6d49f" } } ], "extra": [ 1, 227, 188, 32, 182, 175, 102, 206, 51, 210, 55, 45, 235, 235, 26, 111, 145, 69, 59, 127, 233, 83, 91, 97, 192, 40, 175, 21, 191, 210, 249, 217, 75, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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