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: f5163e8ca6c57af7914324314439a85eef3d335c6e2d035633fe07b23a1da91b
Tx prefix hash: e15502ffc20ec7407e10f5fdf76eed55a7edb2e0e1e7c5c128acec4d5154b6ed
Tx public key: 5ca209de88defacc082fae2c03ecfd634cf312905eb5bfdad26b657ce813450c
| Timestamp: 1780998404 | Timestamp [UTC]: 2026-06-09 09:46:44 | Age [y:d:h:m:s]: 00:008:00:11:24 |
| Block: 8394 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 351 | RingCT/type: yes/0 |
| Extra: 015ca209de88defacc082fae2c03ecfd634cf312905eb5bfdad26b657ce813450c020900000001e49593ff00 | ||
1 output(s) for total of 34.625611220531 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6822220c4468da73b2e535b5599217fe2f30b79fdc0d915b6aac091d44301bf2 | 34.625611220531 | 10376 of 0 | <d0> |
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": 8454,
"vin": [ {
"gen": {
"height": 8394
}
}
],
"vout": [ {
"amount": 34625611220531,
"target": {
"tagged_key": {
"key": "6822220c4468da73b2e535b5599217fe2f30b79fdc0d915b6aac091d44301bf2",
"view_tag": "d0"
}
}
}
],
"extra": [ 1, 92, 162, 9, 222, 136, 222, 250, 204, 8, 47, 174, 44, 3, 236, 253, 99, 76, 243, 18, 144, 94, 181, 191, 218, 210, 107, 101, 124, 232, 19, 69, 12, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}