Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8a860b3ca54ff567dce17b3433d8946da7ba10a2fcc8fd4862b4d63f02ab5eb

Tx prefix hash: 5def5067bd99f27c2ddfe623b13367aa3ff01adabef51bf70eac4cbf8afc1960
Tx public key: e9d1f1d74ae1477f48d9fbc354cce4956575ac22dedf5298d26b1d51ef6d50b9
Timestamp: 1725699295 Timestamp [UCT]: 2024-09-07 08:54:55 Age [y:d:h:m:s]: 00:227:03:22:22
Block: 1104810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162180 RingCT/type: yes/0
Extra: 01e9d1f1d74ae1477f48d9fbc354cce4956575ac22dedf5298d26b1d51ef6d50b9021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 411f776e8790b9e11c8f00769ea03b3dcc87145db76eeac0ace6cb69dca0ff1f 0.600000000000 1582093 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": 1104820, "vin": [ { "gen": { "height": 1104810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "411f776e8790b9e11c8f00769ea03b3dcc87145db76eeac0ace6cb69dca0ff1f" } } ], "extra": [ 1, 233, 209, 241, 215, 74, 225, 71, 127, 72, 217, 251, 195, 84, 204, 228, 149, 101, 117, 172, 34, 222, 223, 82, 152, 210, 107, 29, 81, 239, 109, 80, 185, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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