Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f92e8dd07562972fff14e6f77b23d5c679fbe0c359b6ec4d2be9969e57130b94

Tx prefix hash: fa41c01436fa762457251acab792d2bf1dfc0f51c843cb0f3b267817e1a8f6b0
Tx public key: 14a336ce68deba80fc29ff3f7f8f3dcd158cd257465e4368c4ed8af86fd7f009
Timestamp: 1704233071 Timestamp [UCT]: 2024-01-02 22:04:31 Age [y:d:h:m:s]: 01:081:10:18:54
Block: 926834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319299 RingCT/type: yes/0
Extra: 0114a336ce68deba80fc29ff3f7f8f3dcd158cd257465e4368c4ed8af86fd7f0090211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 254c0da68253fea140aecdd445ef0d706ce125b93b646116f7e562218f9dea1d 0.600000000000 1384632 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": 926844, "vin": [ { "gen": { "height": 926834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "254c0da68253fea140aecdd445ef0d706ce125b93b646116f7e562218f9dea1d" } } ], "extra": [ 1, 20, 163, 54, 206, 104, 222, 186, 128, 252, 41, 255, 63, 127, 143, 61, 205, 21, 140, 210, 87, 70, 94, 67, 104, 196, 237, 138, 248, 111, 215, 240, 9, 2, 17, 0, 0, 0, 3, 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