Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5aede7f1d95da039cd92a2130f61f7e714c5c6dc0234eeb211c27da402a4cac1

Tx prefix hash: 7fc9595d790c4e47884fcb44fd0630a1cfa386ba84ed25424f464e6140cf9526
Tx public key: 784f98d1e3482d5aee12ffc3e9e92daa79f3f65869dd100128aa4bb488240701
Timestamp: 1581287322 Timestamp [UCT]: 2020-02-09 22:28:42 Age [y:d:h:m:s]: 05:024:00:32:09
Block: 61696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1169855 RingCT/type: yes/0
Extra: 01784f98d1e3482d5aee12ffc3e9e92daa79f3f65869dd100128aa4bb48824070102110000000d8a2ee0d9000000000000000000

1 output(s) for total of 383.333131191000 dcy

stealth address amount amount idx
00: 998533d0ea0c05b2d749b6948063253622509f3314475b3709b246c8ebb893c0 383.333131191000 113764 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": 61706, "vin": [ { "gen": { "height": 61696 } } ], "vout": [ { "amount": 383333131191, "target": { "key": "998533d0ea0c05b2d749b6948063253622509f3314475b3709b246c8ebb893c0" } } ], "extra": [ 1, 120, 79, 152, 209, 227, 72, 45, 90, 238, 18, 255, 195, 233, 233, 45, 170, 121, 243, 246, 88, 105, 221, 16, 1, 40, 170, 75, 180, 136, 36, 7, 1, 2, 17, 0, 0, 0, 13, 138, 46, 224, 217, 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