Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb2a48ebae3af460467efae4b6de35f336139cf7ac6ebb2154472edc8331beff

Tx prefix hash: b144b43df316a89c39ac04a02d5e4ff1f34190b0b862b5519e5f958565bd661f
Tx public key: 6b5e7fadb71bc954d9a239c1a6319a9bba241313e358cbf351ba78970139f2be
Timestamp: 1699948807 Timestamp [UCT]: 2023-11-14 08:00:07 Age [y:d:h:m:s]: 01:183:17:40:44
Block: 891326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392511 RingCT/type: yes/0
Extra: 016b5e7fadb71bc954d9a239c1a6319a9bba241313e358cbf351ba78970139f2be02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.683387375000 dcy

stealth address amount amount idx
00: e3a26909770b64dd734a6ec1d0a0f33841ce98c0ca76f60443dcebff4f3bc9d6 0.683387375000 1347365 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": 891336, "vin": [ { "gen": { "height": 891326 } } ], "vout": [ { "amount": 683387375, "target": { "key": "e3a26909770b64dd734a6ec1d0a0f33841ce98c0ca76f60443dcebff4f3bc9d6" } } ], "extra": [ 1, 107, 94, 127, 173, 183, 27, 201, 84, 217, 162, 57, 193, 166, 49, 154, 155, 186, 36, 19, 19, 227, 88, 203, 243, 81, 186, 120, 151, 1, 57, 242, 190, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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