Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e2883c67f67d7cfd130f96532adbfdd26db80f0d670345a022d526f0b740f0a

Tx prefix hash: 2226a5776ddd6a1e3eca347bf4e1ef76bb0508aab66e0537710d9e7392bd966a
Tx public key: c12ac17033b76ed841d40e6cf7854ca1f4d809fd070983bfb9bce79a7c53b9b6
Timestamp: 1751777480 Timestamp [UCT]: 2025-07-06 04:51:20 Age [y:d:h:m:s]: 00:135:18:20:14
Block: 1319714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95409 RingCT/type: yes/0
Extra: 01c12ac17033b76ed841d40e6cf7854ca1f4d809fd070983bfb9bce79a7c53b9b602110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f62e96ca7f8e70e7f5064c2687e0c116d1764ceca6b13d55a2ec4c515572a3c 0.600000000000 1807407 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": 1319724, "vin": [ { "gen": { "height": 1319714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f62e96ca7f8e70e7f5064c2687e0c116d1764ceca6b13d55a2ec4c515572a3c" } } ], "extra": [ 1, 193, 42, 193, 112, 51, 183, 110, 216, 65, 212, 14, 108, 247, 133, 76, 161, 244, 216, 9, 253, 7, 9, 131, 191, 185, 188, 231, 154, 124, 83, 185, 182, 2, 17, 0, 0, 0, 1, 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