Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08ed9e5b4404f348c0416e6026a457be012005d47107a169920aff7f5abe570c

Tx prefix hash: fcb1a5f77e470bb71f9ba752f131c035f4f0628ecd9e213fd9f633680781f979
Tx public key: 4f0adf70168182f8b6512b38079c7093e814131829c84f31f90bbf7dbb56b3d0
Timestamp: 1704173351 Timestamp [UCT]: 2024-01-02 05:29:11 Age [y:d:h:m:s]: 01:099:17:27:56
Block: 926335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332388 RingCT/type: yes/0
Extra: 014f0adf70168182f8b6512b38079c7093e814131829c84f31f90bbf7dbb56b3d00211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acd7ec7f290269f64caf9f56fa3f2786c7ccf278bcc0020342cc7c5a7ed6fa36 0.600000000000 1384117 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": 926345, "vin": [ { "gen": { "height": 926335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acd7ec7f290269f64caf9f56fa3f2786c7ccf278bcc0020342cc7c5a7ed6fa36" } } ], "extra": [ 1, 79, 10, 223, 112, 22, 129, 130, 248, 182, 81, 43, 56, 7, 156, 112, 147, 232, 20, 19, 24, 41, 200, 79, 49, 249, 11, 191, 125, 187, 86, 179, 208, 2, 17, 0, 0, 0, 3, 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