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: 8c79b705f46b27a6968dd9e263647c5d13cd7273ec5ffaf9a9f1160ce9f7d4ea
Tx prefix hash: 087b10863b1bc36a27d16f3f17466f254e34739d8d96ea9f7d974a44c7e1a619
Tx public key: 2a1b75858a06056c1cedb6aac5cafaa829053a376dee7eb087f4a856dfa4e65f
| Timestamp: 1780977811 | Timestamp [UTC]: 2026-06-09 04:03:31 | Age [y:d:h:m:s]: 00:000:08:34:14 |
| Block: 7963 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 617 | RingCT/type: yes/0 |
| Extra: 012a1b75858a06056c1cedb6aac5cafaa829053a376dee7eb087f4a856dfa4e65f020900000001e49593ff00 | ||
1 output(s) for total of 34.654087532174 HMNY
| stealth address | amount | amount idx | tag |
| 00: c8c9cafb48272003acefe92f5a8fab0f73b6aadbfe2fbc4e850355074b1dca9b | 34.654087532174 | 9877 of 0 | <74> |
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": 8023,
"vin": [ {
"gen": {
"height": 7963
}
}
],
"vout": [ {
"amount": 34654087532174,
"target": {
"tagged_key": {
"key": "c8c9cafb48272003acefe92f5a8fab0f73b6aadbfe2fbc4e850355074b1dca9b",
"view_tag": "74"
}
}
}
],
"extra": [ 1, 42, 27, 117, 133, 138, 6, 5, 108, 28, 237, 182, 170, 197, 202, 250, 168, 41, 5, 58, 55, 109, 238, 126, 176, 135, 244, 168, 86, 223, 164, 230, 95, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}