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: e9e6634ff4c6b2e6dcdd4f89815fd279423b5bbb24dc961487da6e21a34b8f7a
Tx prefix hash: 50fa7189c429b009eafd2f485ae60413d1d2a72a4d064b15053f23e2d93a8a4d
Tx public key: 2427351590dc2b6e5b9eedc9835e5601cd4279dfc0f9e4f6af79c8b593069263
| Timestamp: 1780737753 | Timestamp [UTC]: 2026-06-06 09:22:33 | Age [y:d:h:m:s]: 00:002:15:24:14 |
| Block: 6383 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1503 | RingCT/type: yes/0 |
| Extra: 012427351590dc2b6e5b9eedc9835e5601cd4279dfc0f9e4f6af79c8b593069263020900000002e49593ff00 | ||
1 output(s) for total of 34.758679085715 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0bde15b301cd7e2e3055e41a57b3b43db0f17e8618de89a64e7fe9afe400f9cb | 34.758679085715 | 7872 of 0 | <81> |
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": 6443,
"vin": [ {
"gen": {
"height": 6383
}
}
],
"vout": [ {
"amount": 34758679085715,
"target": {
"tagged_key": {
"key": "0bde15b301cd7e2e3055e41a57b3b43db0f17e8618de89a64e7fe9afe400f9cb",
"view_tag": "81"
}
}
}
],
"extra": [ 1, 36, 39, 53, 21, 144, 220, 43, 110, 91, 158, 237, 201, 131, 94, 86, 1, 205, 66, 121, 223, 192, 249, 228, 246, 175, 121, 200, 181, 147, 6, 146, 99, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}