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: 8e1d4950958fbc3839b0534662a33a07b9c203218204dd9883cb499f4c573792
Tx prefix hash: f7cae4d1f77ce4bdce140edec7b72704d7b1dc0703f4989d5229195e251b9f1a
Tx public key: 781844b32b36c46262715f6a3aaa2f5b5edb8607aef53d9a05e10b3414b3b89f
| Timestamp: 1780323063 | Timestamp [UTC]: 2026-06-01 14:11:03 | Age [y:d:h:m:s]: 00:007:09:07:50 |
| Block: 5047 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2839 | RingCT/type: yes/0 |
| Extra: 01781844b32b36c46262715f6a3aaa2f5b5edb8607aef53d9a05e10b3414b3b89f02090000002d26697be300 | ||
1 output(s) for total of 34.847364801389 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0d0bbce605411ad38efdf5b9592eb97ed5b5b879d0a7096b4a4fc0068f32ff2d | 34.847364801389 | 6422 of 0 | <e2> |
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": 5107,
"vin": [ {
"gen": {
"height": 5047
}
}
],
"vout": [ {
"amount": 34847364801389,
"target": {
"tagged_key": {
"key": "0d0bbce605411ad38efdf5b9592eb97ed5b5b879d0a7096b4a4fc0068f32ff2d",
"view_tag": "e2"
}
}
}
],
"extra": [ 1, 120, 24, 68, 179, 43, 54, 196, 98, 98, 113, 95, 106, 58, 170, 47, 91, 94, 219, 134, 7, 174, 245, 61, 154, 5, 225, 11, 52, 20, 179, 184, 159, 2, 9, 0, 0, 0, 45, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}