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: 60e2f2e626a01d2250786d2a39a443012d16481a16a235a5332bf9e23f80644e
Tx prefix hash: 41a5658b5267093b10406f314c7393a3145e5635924e6a24f1a59cb7cd7c6d09
Tx public key: f8308286269b51d6868897a3a16dd038cd1906fd254366f862b7ba9bd6724619
| Timestamp: 1779995665 | Timestamp [UTC]: 2026-05-28 19:14:25 | Age [y:d:h:m:s]: 00:011:06:21:32 |
| Block: 4023 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3863 | RingCT/type: yes/0 |
| Extra: 01f8308286269b51d6868897a3a16dd038cd1906fd254366f862b7ba9bd672461902090000000726697be300 | ||
1 output(s) for total of 34.915492635168 HMNY
| stealth address | amount | amount idx | tag |
| 00: 74585e170b2f3f88e52b3189f20cf2d6bcf2927e0078b0eefd059342334cc515 | 34.915492635168 | 4978 of 0 | <97> |
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": 4083,
"vin": [ {
"gen": {
"height": 4023
}
}
],
"vout": [ {
"amount": 34915492635168,
"target": {
"tagged_key": {
"key": "74585e170b2f3f88e52b3189f20cf2d6bcf2927e0078b0eefd059342334cc515",
"view_tag": "97"
}
}
}
],
"extra": [ 1, 248, 48, 130, 134, 38, 155, 81, 214, 134, 136, 151, 163, 161, 109, 208, 56, 205, 25, 6, 253, 37, 67, 102, 248, 98, 183, 186, 155, 214, 114, 70, 25, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}