Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2016eba558e8be8bb9518aa40cc326e10be0d258205281d7f4b390f48b7570e

Tx prefix hash: 2f8bfc6e0285089ee9c98675425a4f7a4abf850cbd671a2f680442e9975b6977
Tx public key: 060011dacacdfb524b1c68b41c4eb8deb40fb362ad647728481adcf6e6c945c5
Timestamp: 1681685553 Timestamp [UCT]: 2023-04-16 22:52:33 Age [y:d:h:m:s]: 01:151:16:10:37
Block: 740150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369851 RingCT/type: yes/0
Extra: 01060011dacacdfb524b1c68b41c4eb8deb40fb362ad647728481adcf6e6c945c5021100000001b3164c24000000000000000000

1 output(s) for total of 2.165588900000 dcy

stealth address amount amount idx
00: cddbf80def0be16e91f4a804ccd20b4a7d86f6b9d6bd681ba1be773478ecf5a8 2.165588900000 1187031 of 0

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": 740160, "vin": [ { "gen": { "height": 740150 } } ], "vout": [ { "amount": 2165588900, "target": { "key": "cddbf80def0be16e91f4a804ccd20b4a7d86f6b9d6bd681ba1be773478ecf5a8" } } ], "extra": [ 1, 6, 0, 17, 218, 202, 205, 251, 82, 75, 28, 104, 180, 28, 78, 184, 222, 180, 15, 179, 98, 173, 100, 119, 40, 72, 26, 220, 246, 230, 201, 69, 197, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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