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: c3fbf1cdbcc347e716a6f3d39d8d74272bc2a52f00448e984aa747b90c03995b
Tx prefix hash: 33a3c49642cb892c9599cb3dccd2395a85bc339994c1b6dd802833e6a2de526a
Tx public key: 8f263b0423ce5f2b0da622ebb38a382701919f557b47794c13a533170016dd09
| Timestamp: 1780713378 | Timestamp [UTC]: 2026-06-06 02:36:18 | Age [y:d:h:m:s]: 00:011:06:27:39 |
| Block: 6172 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2573 | RingCT/type: yes/0 |
| Extra: 018f263b0423ce5f2b0da622ebb38a382701919f557b47794c13a533170016dd09020900000001e49593ff00 | ||
1 output(s) for total of 34.772670564224 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8a32f8eccfaa41d8331b7c306f4f2397bb2e052c649a8cb517c8e3860d2d97ec | 34.772670564224 | 7649 of 0 | <61> |
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": 6232,
"vin": [ {
"gen": {
"height": 6172
}
}
],
"vout": [ {
"amount": 34772670564224,
"target": {
"tagged_key": {
"key": "8a32f8eccfaa41d8331b7c306f4f2397bb2e052c649a8cb517c8e3860d2d97ec",
"view_tag": "61"
}
}
}
],
"extra": [ 1, 143, 38, 59, 4, 35, 206, 95, 43, 13, 166, 34, 235, 179, 138, 56, 39, 1, 145, 159, 85, 123, 71, 121, 76, 19, 165, 51, 23, 0, 22, 221, 9, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}