Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61554dc69a420d10c8b7a7c0ece1fce1791fe0f6ea7c193a714f45fae5ae2319

Tx prefix hash: 734dc87c89523710709783fd603a6da3ae9efd5c594fe47cdd75b78e063b83af
Tx public key: a7a57793dfd293b82671e921fece790393e7b683c01f91d649b416d36fcda106
Timestamp: 1738303253 Timestamp [UCT]: 2025-01-31 06:00:53 Age [y:d:h:m:s]: 00:040:21:19:02
Block: 1208883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29252 RingCT/type: yes/0
Extra: 01a7a57793dfd293b82671e921fece790393e7b683c01f91d649b416d36fcda1060211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0ff555920ac231cb00c1f2164427cf8e232f602fa7e632234207c22ee645d0c 0.600000000000 1695618 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": 1208893, "vin": [ { "gen": { "height": 1208883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0ff555920ac231cb00c1f2164427cf8e232f602fa7e632234207c22ee645d0c" } } ], "extra": [ 1, 167, 165, 119, 147, 223, 210, 147, 184, 38, 113, 233, 33, 254, 206, 121, 3, 147, 231, 182, 131, 192, 31, 145, 214, 73, 180, 22, 211, 111, 205, 161, 6, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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