Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71d83a66bb370916ad16f48c861278290485aaf57c20f13aebb05b51135c40df

Tx prefix hash: 0fe6f74ccfd7eaac464cb80771a46f45863433c488adf5caa1e15b579d5b2481
Tx public key: 109b1c59f0b734588e3e8c678facd31678cdeef6e8aead3923006a1fd6e492ae
Timestamp: 1686991047 Timestamp [UCT]: 2023-06-17 08:37:27 Age [y:d:h:m:s]: 01:216:10:54:24
Block: 784143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416065 RingCT/type: yes/0
Extra: 01109b1c59f0b734588e3e8c678facd31678cdeef6e8aead3923006a1fd6e492ae021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.548135184000 dcy

stealth address amount amount idx
00: 0c698be1c6bb8dca41b927351878b93b12c9f6c5c899d1dd9192b55c3103f46d 1.548135184000 1234026 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": 784153, "vin": [ { "gen": { "height": 784143 } } ], "vout": [ { "amount": 1548135184, "target": { "key": "0c698be1c6bb8dca41b927351878b93b12c9f6c5c899d1dd9192b55c3103f46d" } } ], "extra": [ 1, 16, 155, 28, 89, 240, 183, 52, 88, 142, 62, 140, 103, 143, 172, 211, 22, 120, 205, 238, 246, 232, 174, 173, 57, 35, 0, 106, 31, 214, 228, 146, 174, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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