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: b24565500239595125c63440dc4a4fc6209bb71c515b694c1454ce27f29bba5f
Tx prefix hash: e7d45cc503aebba9cd4f6596858af3787602e3b6eb532ffc391cdab489a59936
Tx public key: c793bf5e1bbff3c4432683a74606fa626c566d20738fb269b8304d5ea7692181
| Timestamp: 1781014069 | Timestamp [UTC]: 2026-06-09 14:07:49 | Age [y:d:h:m:s]: 00:007:19:07:17 |
| Block: 8616 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 129 | RingCT/type: yes/0 |
| Extra: 01c793bf5e1bbff3c4432683a74606fa626c566d20738fb269b8304d5ea7692181020900000001e49593ff00 | ||
1 output(s) for total of 34.610952739288 HMNY
| stealth address | amount | amount idx | tag |
| 00: 97934bb65a73e9b73d8c854079cf908f1e5ba212ee8f11f953a0c75e050d1e8f | 34.610952739288 | 10648 of 0 | <2a> |
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": 8676,
"vin": [ {
"gen": {
"height": 8616
}
}
],
"vout": [ {
"amount": 34610952739288,
"target": {
"tagged_key": {
"key": "97934bb65a73e9b73d8c854079cf908f1e5ba212ee8f11f953a0c75e050d1e8f",
"view_tag": "2a"
}
}
}
],
"extra": [ 1, 199, 147, 191, 94, 27, 191, 243, 196, 67, 38, 131, 167, 70, 6, 250, 98, 108, 86, 109, 32, 115, 143, 178, 105, 184, 48, 77, 94, 167, 105, 33, 129, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}