Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f05f9a6d2447e3b13c7ad74ee8fed876d72b3dcbdb2d85b3d29db69ea80e0356

Tx prefix hash: 56f0b51626aab8f351dc986511ad751fb4132937bbfec678d9c9af3e1f023886
Tx public key: fd235ef42bdfe52ea163663809fc0894f5d5d6e6c7df4e7409417141efb10fc3
Timestamp: 1737769189 Timestamp [UCT]: 2025-01-25 01:39:49 Age [y:d:h:m:s]: 00:143:14:01:04
Block: 1204679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102363 RingCT/type: yes/0
Extra: 01fd235ef42bdfe52ea163663809fc0894f5d5d6e6c7df4e7409417141efb10fc3021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad92d286bff33870859eb67f40a8c13dd8e47432ed94856d6c91d58e714bc3a6 0.600000000000 1691370 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": 1204689, "vin": [ { "gen": { "height": 1204679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad92d286bff33870859eb67f40a8c13dd8e47432ed94856d6c91d58e714bc3a6" } } ], "extra": [ 1, 253, 35, 94, 244, 43, 223, 229, 46, 161, 99, 102, 56, 9, 252, 8, 148, 245, 213, 214, 230, 199, 223, 78, 116, 9, 65, 113, 65, 239, 177, 15, 195, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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