Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 687d28ac5c5e6198ec73ef899e5051127ec14745978021ec608f17ae3163394e

Tx prefix hash: 4b9f4ecc6c7f8f03936a98cab69c0e44e8408ae3ce163220efe7bc5cbc665971
Tx public key: 6fa7bc9494eb0e50a2ace418ec706f5cef868cb85d194cd7a32c6a8482e63ba8
Timestamp: 1705435054 Timestamp [UCT]: 2024-01-16 19:57:34 Age [y:d:h:m:s]: 01:078:16:38:29
Block: 936787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317340 RingCT/type: yes/0
Extra: 016fa7bc9494eb0e50a2ace418ec706f5cef868cb85d194cd7a32c6a8482e63ba80211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76ab6ce1355d6f2b0cebc17ee78a3e28678974d991d1d243bf091fc087bdd459 0.600000000000 1394827 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": 936797, "vin": [ { "gen": { "height": 936787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76ab6ce1355d6f2b0cebc17ee78a3e28678974d991d1d243bf091fc087bdd459" } } ], "extra": [ 1, 111, 167, 188, 148, 148, 235, 14, 80, 162, 172, 228, 24, 236, 112, 111, 92, 239, 134, 140, 184, 93, 25, 76, 215, 163, 44, 106, 132, 130, 230, 59, 168, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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