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: a53215b41a131463f34ed0934d10e3c560ff1a7b802ba8b4bb46a352e39da436
Tx prefix hash: 765b0121363d46a54a1708cb36d25074a394a6dab2a7f707c4e3c223370e621c
Tx public key: 6023f533d154af1298d86067a2f69ed1d98dfd3248a0fad7333f663d41c7af46
| Timestamp: 1781018825 | Timestamp [UTC]: 2026-06-09 15:27:05 | Age [y:d:h:m:s]: 00:006:01:16:09 |
| Block: 8667 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 78 | RingCT/type: yes/0 |
| Extra: 016023f533d154af1298d86067a2f69ed1d98dfd3248a0fad7333f663d41c7af46020900000002e49593ff00 | ||
1 output(s) for total of 34.607586127001 HMNY
| stealth address | amount | amount idx | tag |
| 00: d8859292b80f3fbe7daca8052b6ff29fa348085f33579bfa459429444cda2adc | 34.607586127001 | 10715 of 0 | <16> |
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": 8727,
"vin": [ {
"gen": {
"height": 8667
}
}
],
"vout": [ {
"amount": 34607586127001,
"target": {
"tagged_key": {
"key": "d8859292b80f3fbe7daca8052b6ff29fa348085f33579bfa459429444cda2adc",
"view_tag": "16"
}
}
}
],
"extra": [ 1, 96, 35, 245, 51, 209, 84, 175, 18, 152, 216, 96, 103, 162, 246, 158, 209, 217, 141, 253, 50, 72, 160, 250, 215, 51, 63, 102, 61, 65, 199, 175, 70, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}