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: fd25daa9d9e2cd227e9d941e29a52520f025b2c3b61eb8d69d1ad193e9108ffb
Tx prefix hash: 2ba4d71c44e28815ac9e9e5571a296915eb6471d8448c8d7269919573c94c1f7
Tx public key: 9693454e16cb4e0b3c5868d9d7fdb789d0d27b075e3ed199029d7d6bafc147c6
| Timestamp: 1779454513 | Timestamp [UTC]: 2026-05-22 12:55:13 | Age [y:d:h:m:s]: 00:017:15:37:49 |
| Block: 367 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7658 | RingCT/type: yes/0 |
| Extra: 019693454e16cb4e0b3c5868d9d7fdb789d0d27b075e3ed199029d7d6bafc147c602090000000293369e7d00 | ||
1 output(s) for total of 35.159818792503 HMNY
| stealth address | amount | amount idx | tag |
| 00: f39dfa391992a734b9ec05a9d2dd8f62a93a644602521f2cc0bce17c2ed23891 | 35.159818792503 | 363 of 0 | <cb> |
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": 427,
"vin": [ {
"gen": {
"height": 367
}
}
],
"vout": [ {
"amount": 35159818792503,
"target": {
"tagged_key": {
"key": "f39dfa391992a734b9ec05a9d2dd8f62a93a644602521f2cc0bce17c2ed23891",
"view_tag": "cb"
}
}
}
],
"extra": [ 1, 150, 147, 69, 78, 22, 203, 78, 11, 60, 88, 104, 217, 215, 253, 183, 137, 208, 210, 123, 7, 94, 62, 209, 153, 2, 157, 125, 107, 175, 193, 71, 198, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}