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: 1b503487103414752a034d1deb6f70a4714cafd62e945909781700e1d22b2f38
Tx prefix hash: bf15e97cb65255c02eae09988ad756d7e20358fe4285e34a55b58781bb1dacd5
Tx public key: 6279e03071870839df6948711b7c14570b30abca901433e5838144016778740f
| Timestamp: 1780323339 | Timestamp [UTC]: 2026-06-01 14:15:39 | Age [y:d:h:m:s]: 00:007:09:03:14 |
| Block: 5112 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2774 | RingCT/type: yes/0 |
| Extra: 016279e03071870839df6948711b7c14570b30abca901433e5838144016778740f02090000004026697be300 | ||
1 output(s) for total of 34.843044770283 HMNY
| stealth address | amount | amount idx | tag |
| 00: 80f8b3fb49887528bec430256ebb2a0bffd889eaf8f3294c556b844fe8582b2d | 34.843044770283 | 6487 of 0 | <7e> |
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": 5172,
"vin": [ {
"gen": {
"height": 5112
}
}
],
"vout": [ {
"amount": 34843044770283,
"target": {
"tagged_key": {
"key": "80f8b3fb49887528bec430256ebb2a0bffd889eaf8f3294c556b844fe8582b2d",
"view_tag": "7e"
}
}
}
],
"extra": [ 1, 98, 121, 224, 48, 113, 135, 8, 57, 223, 105, 72, 113, 27, 124, 20, 87, 11, 48, 171, 202, 144, 20, 51, 229, 131, 129, 68, 1, 103, 120, 116, 15, 2, 9, 0, 0, 0, 64, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}