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: 101d9b6298d20d25e512d02061a9c3f2e31ee16962e4642a3a46b495f034b1ae
Tx prefix hash: 58f419e5dbb0cda8f2924a745c57bd88f28770a025400ff234d3a9cedfe4c5e8
Tx public key: 85694301f4463f8ee0b39c45eb28f6c9cfaae2a34bd9ee181b7c76a6b6d9a0e2
| Timestamp: 1779948339 | Timestamp [UTC]: 2026-05-28 06:05:39 | Age [y:d:h:m:s]: 00:016:04:56:37 |
| Block: 3587 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5158 | RingCT/type: yes/0 |
| Extra: 0185694301f4463f8ee0b39c45eb28f6c9cfaae2a34bd9ee181b7c76a6b6d9a0e202090000000126697be300 | ||
1 output(s) for total of 34.944540602874 HMNY
| stealth address | amount | amount idx | tag |
| 00: f54383361f8e5122a639513d587ab016be643a6e7870acff1cafa9ea00ffa7f3 | 34.944540602874 | 4330 of 0 | <38> |
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": 3647,
"vin": [ {
"gen": {
"height": 3587
}
}
],
"vout": [ {
"amount": 34944540602874,
"target": {
"tagged_key": {
"key": "f54383361f8e5122a639513d587ab016be643a6e7870acff1cafa9ea00ffa7f3",
"view_tag": "38"
}
}
}
],
"extra": [ 1, 133, 105, 67, 1, 244, 70, 63, 142, 224, 179, 156, 69, 235, 40, 246, 201, 207, 170, 226, 163, 75, 217, 238, 24, 27, 124, 118, 166, 182, 217, 160, 226, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}