Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efc19de73d124ff14f0075bc3b6cd7971841e0e3006e576bde385222d7d2b27e

Tx prefix hash: f24f2b720c049cb9933458cf91027486043bb5d716a84b58bc0c3f7496687185
Tx public key: b2adb68488bc4efbc3526c9f23d707eb6e3dfd1f19e3a63c3e5d0c2bc6d7e6f8
Timestamp: 1705264201 Timestamp [UCT]: 2024-01-14 20:30:01 Age [y:d:h:m:s]: 01:064:14:14:26
Block: 935367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307283 RingCT/type: yes/0
Extra: 01b2adb68488bc4efbc3526c9f23d707eb6e3dfd1f19e3a63c3e5d0c2bc6d7e6f80211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70425769b63308ec1c7e6d1ccb9f25e50d751050bb79a18280204d21f247df35 0.600000000000 1393383 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": 935377, "vin": [ { "gen": { "height": 935367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70425769b63308ec1c7e6d1ccb9f25e50d751050bb79a18280204d21f247df35" } } ], "extra": [ 1, 178, 173, 182, 132, 136, 188, 78, 251, 195, 82, 108, 159, 35, 215, 7, 235, 110, 61, 253, 31, 25, 227, 166, 60, 62, 93, 12, 43, 198, 215, 230, 248, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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