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: 7652eff56e0351d331933bbb963908c697e14ec711aaf12c95af202f87bdba75
Tx prefix hash: f20bef631db90425ba81907dbb2fb5c6591cece8999b01a517576f6cbe0fff94
Tx public key: c3e7accd00100badd5f92dc1847ac910e410731c39987fcaeb99f920f2f21b0b
| Timestamp: 1780044720 | Timestamp [UTC]: 2026-05-29 08:52:00 | Age [y:d:h:m:s]: 00:010:16:43:57 |
| Block: 4330 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3556 | RingCT/type: yes/0 |
| Extra: 01c3e7accd00100badd5f92dc1847ac910e410731c39987fcaeb99f920f2f21b0b02090000000326697be300 | ||
1 output(s) for total of 34.895053623091 HMNY
| stealth address | amount | amount idx | tag |
| 00: afab4d2aa44779b05cbccc3af8cc1dc4fcf720e023e0c087ce3c9a26ada6ffdf | 34.895053623091 | 5412 of 0 | <10> |
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": 4390,
"vin": [ {
"gen": {
"height": 4330
}
}
],
"vout": [ {
"amount": 34895053623091,
"target": {
"tagged_key": {
"key": "afab4d2aa44779b05cbccc3af8cc1dc4fcf720e023e0c087ce3c9a26ada6ffdf",
"view_tag": "10"
}
}
}
],
"extra": [ 1, 195, 231, 172, 205, 0, 16, 11, 173, 213, 249, 45, 193, 132, 122, 201, 16, 228, 16, 115, 28, 57, 152, 127, 202, 235, 153, 249, 32, 242, 242, 27, 11, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}