Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5466fe570ff39a3d0ee8da098867a51b8a7f2dee43e666c19e2bde06d953670

Tx prefix hash: 516de07b6c4072fb2bc42b301ab026d9818eec0702be56c7d671fa9fec2a7ef1
Tx public key: 9c764a517b6bbcaced28ad907b63ec4aa9d6ccdca2906f605096a41dd7e1b67b
Timestamp: 1727178741 Timestamp [UCT]: 2024-09-24 11:52:21 Age [y:d:h:m:s]: 00:068:04:52:35
Block: 1117071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48760 RingCT/type: yes/0
Extra: 019c764a517b6bbcaced28ad907b63ec4aa9d6ccdca2906f605096a41dd7e1b67b021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe3de67d88801aee55ac414d67b74c7b650d09c92682eb213950616eb8d0f964 0.600000000000 1597774 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": 1117081, "vin": [ { "gen": { "height": 1117071 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe3de67d88801aee55ac414d67b74c7b650d09c92682eb213950616eb8d0f964" } } ], "extra": [ 1, 156, 118, 74, 81, 123, 107, 188, 172, 237, 40, 173, 144, 123, 99, 236, 74, 169, 214, 204, 220, 162, 144, 111, 96, 80, 150, 164, 29, 215, 225, 182, 123, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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