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: 86fbe70d40c5e503277f8dcfd24d3451b01c94483b0f64a0ccea23dd9256e1dd
Tx prefix hash: 0952e08c8a583a8baebf7a11c0a8e3762784639471e97f084cf50122450d614d
Tx public key: a4359e963756926a648a08719b13b076b790148a7170363dc0f66b1f4096ed8d
| Timestamp: 1780693190 | Timestamp [UTC]: 2026-06-05 20:59:50 | Age [y:d:h:m:s]: 00:003:04:36:07 |
| Block: 5853 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2033 | RingCT/type: yes/0 |
| Extra: 01a4359e963756926a648a08719b13b076b790148a7170363dc0f66b1f4096ed8d020900000001e49593ff00 | ||
1 output(s) for total of 34.793834252422 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8ad16796e6d52f9a793d25a076f907eea4d4842c2173aa1fae84ab06ed339440 | 34.793834252422 | 7312 of 0 | <cd> |
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": 5913,
"vin": [ {
"gen": {
"height": 5853
}
}
],
"vout": [ {
"amount": 34793834252422,
"target": {
"tagged_key": {
"key": "8ad16796e6d52f9a793d25a076f907eea4d4842c2173aa1fae84ab06ed339440",
"view_tag": "cd"
}
}
}
],
"extra": [ 1, 164, 53, 158, 150, 55, 86, 146, 106, 100, 138, 8, 113, 155, 19, 176, 118, 183, 144, 20, 138, 113, 112, 54, 61, 192, 246, 107, 31, 64, 150, 237, 141, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}