Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d78dd7e761a141980a9a5e7d368bdddf93d69e93f6b0edd0bb77185b8be9b61a

Tx prefix hash: 5f9fa30c722f53eade6497b978de4871deca5b90445da3b3c8ef63853d6d90ff
Tx public key: 7ef8adccae0125d99dcfdb80464b7e8f8a75b531b871b0fbe9f9a1ab2677d34c
Timestamp: 1688263167 Timestamp [UCT]: 2023-07-02 01:59:27 Age [y:d:h:m:s]: 01:328:06:35:18
Block: 794700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495800 RingCT/type: yes/0
Extra: 017ef8adccae0125d99dcfdb80464b7e8f8a75b531b871b0fbe9f9a1ab2677d34c0211000000024b8f5122000000000000000000

1 output(s) for total of 1.428331921000 dcy

stealth address amount amount idx
00: 9b7785394a9c2a71d72916a6669ccfd5e8dc1e7e5c8732b7108c333632db26a9 1.428331921000 1245467 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": 794710, "vin": [ { "gen": { "height": 794700 } } ], "vout": [ { "amount": 1428331921, "target": { "key": "9b7785394a9c2a71d72916a6669ccfd5e8dc1e7e5c8732b7108c333632db26a9" } } ], "extra": [ 1, 126, 248, 173, 204, 174, 1, 37, 217, 157, 207, 219, 128, 70, 75, 126, 143, 138, 117, 181, 49, 184, 113, 176, 251, 233, 249, 161, 171, 38, 119, 211, 76, 2, 17, 0, 0, 0, 2, 75, 143, 81, 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