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: f43181677c6fb929a75fad94836696502a020acd9bda6c8053e5aec2d985310a
Tx prefix hash: ef4795f140575ad49ea1ba87c14ccecced0324e928be93627ef17f74d42fb985
Tx public key: e5452291a2bb8b8bf11a898ee053603bfa4851cb5a15364e49ae476516b84ac3
| Timestamp: 1780817865 | Timestamp [UTC]: 2026-06-07 07:37:45 | Age [y:d:h:m:s]: 00:001:17:09:02 |
| Block: 7098 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 788 | RingCT/type: yes/0 |
| Extra: 01e5452291a2bb8b8bf11a898ee053603bfa4851cb5a15364e49ae476516b84ac3020900000003e49593ff00 | ||
1 output(s) for total of 34.711309051316 HMNY
| stealth address | amount | amount idx | tag |
| 00: ea579034c64417741b5ad3352c1b7822f440b6f155c719c67c0b1f7956709ba7 | 34.711309051316 | 8750 of 0 | <b8> |
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": 7158,
"vin": [ {
"gen": {
"height": 7098
}
}
],
"vout": [ {
"amount": 34711309051316,
"target": {
"tagged_key": {
"key": "ea579034c64417741b5ad3352c1b7822f440b6f155c719c67c0b1f7956709ba7",
"view_tag": "b8"
}
}
}
],
"extra": [ 1, 229, 69, 34, 145, 162, 187, 139, 139, 241, 26, 137, 142, 224, 83, 96, 59, 250, 72, 81, 203, 90, 21, 54, 78, 73, 174, 71, 101, 22, 184, 74, 195, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}