Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57c828b07994267b737ff59909a98289c7e423acbdc999b4506df7940012a545

Tx prefix hash: ec6f3b28f8cdc3061df7f78cc203a9848b642ad2313af5772ec4c53417f92537
Tx public key: 2663b4da8dc874b74833d325080b3645ba8f407aa01561df02b43ba179bd3f6c
Timestamp: 1708271362 Timestamp [UCT]: 2024-02-18 15:49:22 Age [y:d:h:m:s]: 01:007:20:11:32
Block: 960320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266597 RingCT/type: yes/0
Extra: 012663b4da8dc874b74833d325080b3645ba8f407aa01561df02b43ba179bd3f6c02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0eda58d9c9adc36ed2cd70e47eb5d758de22e9e5ef28df67cfb2422a4193ca0 0.600000000000 1419883 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": 960330, "vin": [ { "gen": { "height": 960320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0eda58d9c9adc36ed2cd70e47eb5d758de22e9e5ef28df67cfb2422a4193ca0" } } ], "extra": [ 1, 38, 99, 180, 218, 141, 200, 116, 183, 72, 51, 211, 37, 8, 11, 54, 69, 186, 143, 64, 122, 160, 21, 97, 223, 2, 180, 59, 161, 121, 189, 63, 108, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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