Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0522f1999de6a07c2287ad7ebcebbd3ef5c309deb7eca174f5e058dbcd284ab

Tx prefix hash: 705b4cb94c910087c1ce3b3dd2fdca32a9ccd70fa611ea3311d31a338c8d5e1c
Tx public key: 2e4245673c7e86ae3314082dbe9fe56a736ba5ee14de43c023b0b3a78686dbfd
Timestamp: 1708060076 Timestamp [UCT]: 2024-02-16 05:07:56 Age [y:d:h:m:s]: 01:087:16:06:23
Block: 958559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323730 RingCT/type: yes/0
Extra: 012e4245673c7e86ae3314082dbe9fe56a736ba5ee14de43c023b0b3a78686dbfd0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: adbd5af3300ba564dbf6694f9a763f883fef3b34cc3a85fc5c876746c43d3387 0.600000000000 1417918 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": 958569, "vin": [ { "gen": { "height": 958559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "adbd5af3300ba564dbf6694f9a763f883fef3b34cc3a85fc5c876746c43d3387" } } ], "extra": [ 1, 46, 66, 69, 103, 60, 126, 134, 174, 51, 20, 8, 45, 190, 159, 229, 106, 115, 107, 165, 238, 20, 222, 67, 192, 35, 176, 179, 167, 134, 134, 219, 253, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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