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: 0e551b822931fea891a2bb51fb5ae2be9b5579e4b1b28ddafebe1cf566612279
Tx prefix hash: 6050ae24c7603a88f12fae7a9a4bb12e7c156b64648fa71fd7d1c04e089baeb5
Tx public key: fb5df8896427867941e1ac2b0cd21dd9ff3bbc477e611919f5b503432adc7a31
| Timestamp: 1780687585 | Timestamp [UTC]: 2026-06-05 19:26:25 | Age [y:d:h:m:s]: 00:003:03:52:28 |
| Block: 5489 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2397 | RingCT/type: yes/0 |
| Extra: 01fb5df8896427867941e1ac2b0cd21dd9ff3bbc477e611919f5b503432adc7a31020900000001e49593ff00 | ||
1 output(s) for total of 34.817999148915 HMNY
| stealth address | amount | amount idx | tag |
| 00: a4cf14f7ce09c7a285340780d6f96a16c7860799dd334e98a31d8191fb56ec21 | 34.817999148915 | 6928 of 0 | <a4> |
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": 5549,
"vin": [ {
"gen": {
"height": 5489
}
}
],
"vout": [ {
"amount": 34817999148915,
"target": {
"tagged_key": {
"key": "a4cf14f7ce09c7a285340780d6f96a16c7860799dd334e98a31d8191fb56ec21",
"view_tag": "a4"
}
}
}
],
"extra": [ 1, 251, 93, 248, 137, 100, 39, 134, 121, 65, 225, 172, 43, 12, 210, 29, 217, 255, 59, 188, 71, 126, 97, 25, 25, 245, 181, 3, 67, 42, 220, 122, 49, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}