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: f5a6fc975ac1171b4a977e4ed54af5aa0c4fec8833c01b9b3cd715eb996bf49a
Tx prefix hash: 2626634c69573e753d89db6cada795d0ebc2c872a7bf3893ea9115a854c53d94
Tx public key: 7bc5130ad4ef1f32ba9fbf4c5c8a6fe9f48beaf7be5ceec426f56c86505f2032
| Timestamp: 1779870321 | Timestamp [UTC]: 2026-05-27 08:25:21 | Age [y:d:h:m:s]: 00:012:16:21:26 |
| Block: 2796 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5090 | RingCT/type: yes/0 |
| Extra: 017bc5130ad4ef1f32ba9fbf4c5c8a6fe9f48beaf7be5ceec426f56c86505f203202090000000226697be300 | ||
1 output(s) for total of 34.997301718466 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2c394d889a4297e977a41acf86f6c6030e546d21c6de974484accd02edb01c8f | 34.997301718466 | 3308 of 0 | <d0> |
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": 2856,
"vin": [ {
"gen": {
"height": 2796
}
}
],
"vout": [ {
"amount": 34997301718466,
"target": {
"tagged_key": {
"key": "2c394d889a4297e977a41acf86f6c6030e546d21c6de974484accd02edb01c8f",
"view_tag": "d0"
}
}
}
],
"extra": [ 1, 123, 197, 19, 10, 212, 239, 31, 50, 186, 159, 191, 76, 92, 138, 111, 233, 244, 139, 234, 247, 190, 92, 238, 196, 38, 245, 108, 134, 80, 95, 32, 50, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}