Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7af29850af4bd0740fb1ea5a72a62c07d62ba3939cebf4748e671125605388bf

Tx prefix hash: d960a6c056ea94a4971e544fc67a433566c9eb5c6b652cdf7b2442bca04b6132
Tx public key: 89efdeadfdd186b1f5cb7289ba3f5f89cb9e023fe3e5203f1a510fcbb81ad8ac
Timestamp: 1749301713 Timestamp [UCT]: 2025-06-07 13:08:33 Age [y:d:h:m:s]: 00:160:07:08:21
Block: 1299939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112240 RingCT/type: yes/0
Extra: 0189efdeadfdd186b1f5cb7289ba3f5f89cb9e023fe3e5203f1a510fcbb81ad8ac021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79e81648bae6d52784575d82f60ddce2437c95f25520d1356cd910e3d5742e58 0.600000000000 1787482 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": 1299949, "vin": [ { "gen": { "height": 1299939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79e81648bae6d52784575d82f60ddce2437c95f25520d1356cd910e3d5742e58" } } ], "extra": [ 1, 137, 239, 222, 173, 253, 209, 134, 177, 245, 203, 114, 137, 186, 63, 95, 137, 203, 158, 2, 63, 227, 229, 32, 63, 26, 81, 15, 203, 184, 26, 216, 172, 2, 17, 0, 0, 0, 1, 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