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: 82435c4a7a87fbc74842777c103d44371996a5fc91ceee11b33c43ce0ae27913
Tx prefix hash: b42d969f53aac8229106002faf20e153cf212e5098532d3679723dfa8ef88886
Tx public key: 85873901f3dba9c2956b8f9ac2bee9cfb089e4ad9d9f47934f0f2e6e60a59c03
| Timestamp: 1780708678 | Timestamp [UTC]: 2026-06-06 01:17:58 | Age [y:d:h:m:s]: 00:003:00:17:59 |
| Block: 6141 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1745 | RingCT/type: yes/0 |
| Extra: 0185873901f3dba9c2956b8f9ac2bee9cfb089e4ad9d9f47934f0f2e6e60a59c03020900000001e49593ff00 | ||
1 output(s) for total of 34.774726658746 HMNY
| stealth address | amount | amount idx | tag |
| 00: d5afeeba74b940d4007fbcc90a29b206836afc5ce1e6986370d3d721e4e0b86e | 34.774726658746 | 7616 of 0 | <ca> |
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": 6201,
"vin": [ {
"gen": {
"height": 6141
}
}
],
"vout": [ {
"amount": 34774726658746,
"target": {
"tagged_key": {
"key": "d5afeeba74b940d4007fbcc90a29b206836afc5ce1e6986370d3d721e4e0b86e",
"view_tag": "ca"
}
}
}
],
"extra": [ 1, 133, 135, 57, 1, 243, 219, 169, 194, 149, 107, 143, 154, 194, 190, 233, 207, 176, 137, 228, 173, 157, 159, 71, 147, 79, 15, 46, 110, 96, 165, 156, 3, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}