Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76f64d137d8b327641fff85fcaf1ea6d3c117a1c860219acf87b8196e4d3f89a

Tx prefix hash: 799d54530aabf838a12fd06041e88e270355dd44ab1401326fcfa7fe0ee864fb
Tx public key: e8ec0498c3118ddcc802b47add170418d32da6d71b6b69c9f61ad88fb85b7490
Timestamp: 1706799537 Timestamp [UCT]: 2024-02-01 14:58:57 Age [y:d:h:m:s]: 01:070:17:09:52
Block: 948100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311618 RingCT/type: yes/0
Extra: 01e8ec0498c3118ddcc802b47add170418d32da6d71b6b69c9f61ad88fb85b749002110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb9cdd6ac15298f2aa99e4cfc10758d17bb8d53f8a0fe5b1ac56b6ffe9f85a2f 0.600000000000 1406472 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": 948110, "vin": [ { "gen": { "height": 948100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb9cdd6ac15298f2aa99e4cfc10758d17bb8d53f8a0fe5b1ac56b6ffe9f85a2f" } } ], "extra": [ 1, 232, 236, 4, 152, 195, 17, 141, 220, 200, 2, 180, 122, 221, 23, 4, 24, 211, 45, 166, 215, 27, 107, 105, 201, 246, 26, 216, 143, 184, 91, 116, 144, 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