Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffe37669c0862948b464b9fe24b5d3c5a1acaf707464ead1cfba813a9f158304

Tx prefix hash: 8a3f1518ebcdc9dc6282eb807a002c0f03a3e8e63274e0ad4dbc97f34c171214
Tx public key: 22f3db7244f2d9d6338b09f867db8c79401987fc59adc5240012130c2299c0a7
Timestamp: 1677776873 Timestamp [UCT]: 2023-03-02 17:07:53 Age [y:d:h:m:s]: 02:251:17:53:59
Block: 708391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 699206 RingCT/type: yes/0
Extra: 0122f3db7244f2d9d6338b09f867db8c79401987fc59adc5240012130c2299c0a7021100000002835e4d22000000000000000000

1 output(s) for total of 2.759347842000 dcy

stealth address amount amount idx
00: 8f4fc463cd7b4f88ea41cf61dfd2389a7b7a293fc1fe956e971a7feb122eeec9 2.759347842000 1152274 of 0

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": 708401, "vin": [ { "gen": { "height": 708391 } } ], "vout": [ { "amount": 2759347842, "target": { "key": "8f4fc463cd7b4f88ea41cf61dfd2389a7b7a293fc1fe956e971a7feb122eeec9" } } ], "extra": [ 1, 34, 243, 219, 114, 68, 242, 217, 214, 51, 139, 9, 248, 103, 219, 140, 121, 64, 25, 135, 252, 89, 173, 197, 36, 0, 18, 19, 12, 34, 153, 192, 167, 2, 17, 0, 0, 0, 2, 131, 94, 77, 34, 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