For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: 09dfe4d0841b7ebe2e4e94812bf6190394c60a81da4adf36e7af3d4cee7aac6a
Tx prefix hash: 6e68d93a560f1641995798d56b09dd9f65d9367bed1f49a71673bf5b55f5c36d
Tx public key: 13ff8fd83279087158724cd671a7682b91a7da7db0c9af70e221fcac72d53c2c
| Timestamp: 1780691248 | Timestamp [UTC]: 2026-06-05 20:27:28 | Age [y:d:h:m:s]: 00:003:05:08:29 |
| Block: 5717 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2169 | RingCT/type: yes/0 |
| Extra: 0113ff8fd83279087158724cd671a7682b91a7da7db0c9af70e221fcac72d53c2c020900000001e49593ff00 | ||
1 output(s) for total of 34.802860931956 HMNY
| stealth address | amount | amount idx | tag |
| 00: d017156bde8514dfc386bf6a2c0eb6c029644f12d49429098b4def45db343b95 | 34.802860931956 | 7168 of 0 | <59> |
Check which outputs belong to given HMNY 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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-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": 5777,
"vin": [ {
"gen": {
"height": 5717
}
}
],
"vout": [ {
"amount": 34802860931956,
"target": {
"tagged_key": {
"key": "d017156bde8514dfc386bf6a2c0eb6c029644f12d49429098b4def45db343b95",
"view_tag": "59"
}
}
}
],
"extra": [ 1, 19, 255, 143, 216, 50, 121, 8, 113, 88, 114, 76, 214, 113, 167, 104, 43, 145, 167, 218, 125, 176, 201, 175, 112, 226, 33, 252, 172, 114, 213, 60, 44, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}