Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28565e1431e2b824bb1305f4da2e2a5358f7942ff478f1e006e2cc1a67a95d08

Tx prefix hash: 193959cc95138c8e5353012553a7edb5260c01cb386d6859b0378d134c573a5f
Tx public key: 6311ec3d8ba31e1b379baffe31f7207a1ff48ec8a7ebcdc02e37e3b886209a21
Timestamp: 1695568826 Timestamp [UCT]: 2023-09-24 15:20:26 Age [y:d:h:m:s]: 01:194:19:29:57
Block: 855204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400303 RingCT/type: yes/0
Extra: 016311ec3d8ba31e1b379baffe31f7207a1ff48ec8a7ebcdc02e37e3b886209a210211000000034b8f5122000000000000000000

1 output(s) for total of 0.900231458000 dcy

stealth address amount amount idx
00: 659c0c957d97335fe19d17c3ff6ede7b7ee50ad1637b3aa50965fdbd075fa5c9 0.900231458000 1309210 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": 855214, "vin": [ { "gen": { "height": 855204 } } ], "vout": [ { "amount": 900231458, "target": { "key": "659c0c957d97335fe19d17c3ff6ede7b7ee50ad1637b3aa50965fdbd075fa5c9" } } ], "extra": [ 1, 99, 17, 236, 61, 139, 163, 30, 27, 55, 155, 175, 254, 49, 247, 32, 122, 31, 244, 142, 200, 167, 235, 205, 192, 46, 55, 227, 184, 134, 32, 154, 33, 2, 17, 0, 0, 0, 3, 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