Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cfffbc34a8d429288a8d77c3f31eee41f7476c3eaf1bd6dbed7dd2fd9f4e5f2

Tx prefix hash: fdfea84d37e201cbb6ab742780d1dd18967e29264b6e6621903d3d19d1b6622b
Tx public key: 464ab2d7c7e2d42c5314b2db06571838446195715089cc3f56b47e93b1baabca
Timestamp: 1580118290 Timestamp [UCT]: 2020-01-27 09:44:50 Age [y:d:h:m:s]: 04:284:01:00:36
Block: 53886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1093151 RingCT/type: yes/0
Extra: 01464ab2d7c7e2d42c5314b2db06571838446195715089cc3f56b47e93b1baabca021100000001b221b3d1000000000000000000

1 output(s) for total of 406.895357759000 dcy

stealth address amount amount idx
00: b081b6a0d55ebb848ed6fd91145e39026713ce970044f0e0dc13c0b697927304 406.895357759000 99847 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": 53896, "vin": [ { "gen": { "height": 53886 } } ], "vout": [ { "amount": 406895357759, "target": { "key": "b081b6a0d55ebb848ed6fd91145e39026713ce970044f0e0dc13c0b697927304" } } ], "extra": [ 1, 70, 74, 178, 215, 199, 226, 212, 44, 83, 20, 178, 219, 6, 87, 24, 56, 68, 97, 149, 113, 80, 137, 204, 63, 86, 180, 126, 147, 177, 186, 171, 202, 2, 17, 0, 0, 0, 1, 178, 33, 179, 209, 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