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: 6d7ed68e3329a6e4cb41ddc6270c4169ae4e5b2b2f1e287b8a9df27d6cb94618
Tx prefix hash: 1f8d276fb090f759c033409702926d3be8e3ff99053c6a34db2c10d9016f1e4d
Tx public key: ce5a3ff45e64d94bc0c17541728737264f28cb31f92af2fc5aaae94b7245d9b6
| Timestamp: 1779637836 | Timestamp [UTC]: 2026-05-24 15:50:36 | Age [y:d:h:m:s]: 00:015:12:42:26 |
| Block: 1174 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6853 | RingCT/type: yes/0 |
| Extra: 01ce5a3ff45e64d94bc0c17541728737264f28cb31f92af2fc5aaae94b7245d9b6020900000001ba6d17be00 | ||
1 output(s) for total of 35.105741310389 HMNY
| stealth address | amount | amount idx | tag |
| 00: 72291d5629d056b746c9003cd6c3dd3ee7bb6279848dda8e66157225e953e415 | 35.105741310389 | 1318 of 0 | <23> |
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": 1234,
"vin": [ {
"gen": {
"height": 1174
}
}
],
"vout": [ {
"amount": 35105741310389,
"target": {
"tagged_key": {
"key": "72291d5629d056b746c9003cd6c3dd3ee7bb6279848dda8e66157225e953e415",
"view_tag": "23"
}
}
}
],
"extra": [ 1, 206, 90, 63, 244, 94, 100, 217, 75, 192, 193, 117, 65, 114, 135, 55, 38, 79, 40, 203, 49, 249, 42, 242, 252, 90, 170, 233, 75, 114, 69, 217, 182, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}