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: 004b48c98f874b388fa64e0180ca0c2a688d5401f4a6dac41479262447a8606e
Tx prefix hash: 546e7bec47182ce373d371f303f5d4338d34a793df226cef8d38f36accd1f0b4
Tx public key: 0af78bafbfae71074b3cd28f181d65c188932d055d322f4b8969473ae86f5a99
| Timestamp: 1780748696 | Timestamp [UTC]: 2026-06-06 12:24:56 | Age [y:d:h:m:s]: 00:002:08:47:11 |
| Block: 6469 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1417 | RingCT/type: yes/0 |
| Extra: 010af78bafbfae71074b3cd28f181d65c188932d055d322f4b8969473ae86f5a99020900000001e49593ff00 | ||
1 output(s) for total of 34.752978012833 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0c40e0b9187901431d37e3779679785629f3ca7f41e3fdd00721d486522e823e | 34.752978012833 | 7964 of 0 | <6e> |
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": 6529,
"vin": [ {
"gen": {
"height": 6469
}
}
],
"vout": [ {
"amount": 34752978012833,
"target": {
"tagged_key": {
"key": "0c40e0b9187901431d37e3779679785629f3ca7f41e3fdd00721d486522e823e",
"view_tag": "6e"
}
}
}
],
"extra": [ 1, 10, 247, 139, 175, 191, 174, 113, 7, 75, 60, 210, 143, 24, 29, 101, 193, 136, 147, 45, 5, 93, 50, 47, 75, 137, 105, 71, 58, 232, 111, 90, 153, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}