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: 603d072453d284e2e68616f0b109fb80e369fc0359c940207fb6d4e5ded57b36
Tx prefix hash: 623ae9b69d894daa63056e747ed4b90f0b477dbf7e0f59ff94adb96024aa77e7
Tx public key: 724fad55282f3f0c9b6edf0c6a4a5d9ca00789d54d079e2156219559dee2073c
| Timestamp: 1780689441 | Timestamp [UTC]: 2026-06-05 19:57:21 | Age [y:d:h:m:s]: 00:003:05:38:36 |
| Block: 5595 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2291 | RingCT/type: yes/0 |
| Extra: 01724fad55282f3f0c9b6edf0c6a4a5d9ca00789d54d079e2156219559dee2073c020900000001e49593ff00 | ||
1 output(s) for total of 34.810960387085 HMNY
| stealth address | amount | amount idx | tag |
| 00: ef162c5822e3112f1a754b48a065c666b43890d5afa038ef78762883a01a950b | 34.810960387085 | 7040 of 0 | <ec> |
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": 5655,
"vin": [ {
"gen": {
"height": 5595
}
}
],
"vout": [ {
"amount": 34810960387085,
"target": {
"tagged_key": {
"key": "ef162c5822e3112f1a754b48a065c666b43890d5afa038ef78762883a01a950b",
"view_tag": "ec"
}
}
}
],
"extra": [ 1, 114, 79, 173, 85, 40, 47, 63, 12, 155, 110, 223, 12, 106, 74, 93, 156, 160, 7, 137, 213, 77, 7, 158, 33, 86, 33, 149, 89, 222, 226, 7, 60, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}