Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c493cc4813c8e54eeceb14a022e6cf71fdf404def5c1a5bb9eef78824374ee77

Tx prefix hash: 38517437d99441d43c14fb2a3c6c65d2b8d792e4932ce294d89a0c44750d48d3
Tx public key: e015e2ee5be5e1423c84946ca9c36ba19ec3bdfd2c94688bb04b060698c91551
Timestamp: 1726349232 Timestamp [UCT]: 2024-09-14 21:27:12 Age [y:d:h:m:s]: 00:161:13:16:10
Block: 1110187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115258 RingCT/type: yes/0
Extra: 01e015e2ee5be5e1423c84946ca9c36ba19ec3bdfd2c94688bb04b060698c91551021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69c3309beeb2fb530cb2810bdeb4e301af25f53b822dfa7642603d9b23d4df1c 0.600000000000 1588704 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": 1110197, "vin": [ { "gen": { "height": 1110187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69c3309beeb2fb530cb2810bdeb4e301af25f53b822dfa7642603d9b23d4df1c" } } ], "extra": [ 1, 224, 21, 226, 238, 91, 229, 225, 66, 60, 132, 148, 108, 169, 195, 107, 161, 158, 195, 189, 253, 44, 148, 104, 139, 176, 75, 6, 6, 152, 201, 21, 81, 2, 17, 0, 0, 0, 6, 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