Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ce77a8e0aaf1570a189f78af8a51f53548f4a7987bdc3dac4b9f5696b3acf57

Tx prefix hash: 8ad491c3a5197c11a445131a6dd2dedececa34e9c237bfde52f62cd8910eaa94
Tx public key: 987d67f5e8b626406da701746ace8b6c51b59713bc498554f8b87a0333c24557
Timestamp: 1718981536 Timestamp [UCT]: 2024-06-21 14:52:16 Age [y:d:h:m:s]: 01:133:19:30:03
Block: 1049093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354199 RingCT/type: yes/0
Extra: 01987d67f5e8b626406da701746ace8b6c51b59713bc498554f8b87a0333c2455702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df717c575b3feaddc1b38b6caaf8aa3410c2d4e4b7136a174e12725dd432ee5c 0.600000000000 1519190 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": 1049103, "vin": [ { "gen": { "height": 1049093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df717c575b3feaddc1b38b6caaf8aa3410c2d4e4b7136a174e12725dd432ee5c" } } ], "extra": [ 1, 152, 125, 103, 245, 232, 182, 38, 64, 109, 167, 1, 116, 106, 206, 139, 108, 81, 181, 151, 19, 188, 73, 133, 84, 248, 184, 122, 3, 51, 194, 69, 87, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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