Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0eb626e3eb87c5fb18c6ed141942337c46713234b26a0c2f366a0acf116cff7e

Tx prefix hash: 04eb427e3b0faf6ea1213c2074c3c31a55e7e067d604f27ffd88fa954badc9e3
Tx public key: e904a9c1a1b0e526275f2202c1b44fc8a63aa1dc9895884c82f2223c5fbfe324
Timestamp: 1735001585 Timestamp [UCT]: 2024-12-24 00:53:05 Age [y:d:h:m:s]: 00:095:06:21:07
Block: 1181815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67858 RingCT/type: yes/0
Extra: 01e904a9c1a1b0e526275f2202c1b44fc8a63aa1dc9895884c82f2223c5fbfe3240211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58e8cbe9ea8302c57b0b1fe4683164f0a1cc4babb4c38d0210de84fc0a95c21f 0.600000000000 1668242 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": 1181825, "vin": [ { "gen": { "height": 1181815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58e8cbe9ea8302c57b0b1fe4683164f0a1cc4babb4c38d0210de84fc0a95c21f" } } ], "extra": [ 1, 233, 4, 169, 193, 161, 176, 229, 38, 39, 95, 34, 2, 193, 180, 79, 200, 166, 58, 161, 220, 152, 149, 136, 76, 130, 242, 34, 60, 95, 191, 227, 36, 2, 17, 0, 0, 0, 5, 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