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: 6e7e321a2f76872b58ed4bb4561b933b1f21b556a7816f69fe4cb96bcc92d0f5
Tx prefix hash: bb9be946f12da7951ffd75314d2e7d0e47f6d7b22206c70f722a77ad49d585a4
Tx public key: caf5ed984c38035f02acee1ff5b8650d815e27761f90bbde52d474c80b087653
| Timestamp: 1779431484 | Timestamp [UTC]: 2026-05-22 06:31:24 | Age [y:d:h:m:s]: 00:017:15:53:25 |
| Block: 22 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0801 kB |
| Tx version: 2 | No of confirmations: 7864 | RingCT/type: yes/0 |
| Extra: 01caf5ed984c38035f02acee1ff5b8650d815e27761f90bbde52d474c80b087653 | ||
1 output(s) for total of 35.182962829681 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0d44e062a970a443b0a7db72810ce5a33364d5235bf5913d72a365d72c858aa0 | 35.182962829681 | 18 of 0 | <d6> |
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": 82,
"vin": [ {
"gen": {
"height": 22
}
}
],
"vout": [ {
"amount": 35182962829681,
"target": {
"tagged_key": {
"key": "0d44e062a970a443b0a7db72810ce5a33364d5235bf5913d72a365d72c858aa0",
"view_tag": "d6"
}
}
}
],
"extra": [ 1, 202, 245, 237, 152, 76, 56, 3, 95, 2, 172, 238, 31, 245, 184, 101, 13, 129, 94, 39, 118, 31, 144, 187, 222, 82, 212, 116, 200, 11, 8, 118, 83
],
"rct_signatures": {
"type": 0
}
}