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: 69649480459fa77ccdcccf2f7dfb7d69278c3910d7cdb118aa9a87acac49e9ec
Tx prefix hash: 5928022a1be4c33d7b954f55b049c4000c265826a1ffde229de7cd30bc577952
Tx public key: efd4ee043738d55126a78987f727cb41aa71e947fabd1128f663ea8dea5c5b6d
| Timestamp: 1779447824 | Timestamp [UTC]: 2026-05-22 11:03:44 | Age [y:d:h:m:s]: 00:017:15:46:04 |
| Block: 290 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7630 | RingCT/type: yes/0 |
| Extra: 01efd4ee043738d55126a78987f727cb41aa71e947fabd1128f663ea8dea5c5b6d0209000000014438f87f00 | ||
1 output(s) for total of 35.164982953125 HMNY
| stealth address | amount | amount idx | tag |
| 00: fcea649db46658ca955641a282549bbbf5ff63790f9a7477d631ebb76862c6e9 | 35.164982953125 | 286 of 0 | <d1> |
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": 350,
"vin": [ {
"gen": {
"height": 290
}
}
],
"vout": [ {
"amount": 35164982953125,
"target": {
"tagged_key": {
"key": "fcea649db46658ca955641a282549bbbf5ff63790f9a7477d631ebb76862c6e9",
"view_tag": "d1"
}
}
}
],
"extra": [ 1, 239, 212, 238, 4, 55, 56, 213, 81, 38, 167, 137, 135, 247, 39, 203, 65, 170, 113, 233, 71, 250, 189, 17, 40, 246, 99, 234, 141, 234, 92, 91, 109, 2, 9, 0, 0, 0, 1, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}