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: 31e19df37193d354fe49f9b30219242462c40f4e6b20dc7eccfc71359bc9baa2
Tx prefix hash: 417d5166a6e5e59020d9edf1adccaf305dd6785845d641a236801c4a9bbde78c
Tx public key: fa2d12838a4b731fe7d2c39995776255651b3b560e963b2df2c6151a3ac1b996
| Timestamp: 1779973830 | Timestamp [UTC]: 2026-05-28 13:10:30 | Age [y:d:h:m:s]: 00:011:13:30:06 |
| Block: 3869 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4027 | RingCT/type: yes/0 |
| Extra: 01fa2d12838a4b731fe7d2c39995776255651b3b560e963b2df2c6151a3ac1b99602090000000326697be300 | ||
1 output(s) for total of 34.925749937964 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9fa7406569280e7d0bf431fd39889963388686950ad2dbdd47072ccf22664864 | 34.925749937964 | 4731 of 0 | <4f> |
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": 3929,
"vin": [ {
"gen": {
"height": 3869
}
}
],
"vout": [ {
"amount": 34925749937964,
"target": {
"tagged_key": {
"key": "9fa7406569280e7d0bf431fd39889963388686950ad2dbdd47072ccf22664864",
"view_tag": "4f"
}
}
}
],
"extra": [ 1, 250, 45, 18, 131, 138, 75, 115, 31, 231, 210, 195, 153, 149, 119, 98, 85, 101, 27, 59, 86, 14, 150, 59, 45, 242, 198, 21, 26, 58, 193, 185, 150, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}