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: ac3ecc41357c1b2901e765318f956a0ad019dfb2aa22b04ba8b66f3617a0d660
Tx prefix hash: 71b8f3ef0b16bfb465b3c97814b0411c8b54f9073c57f81b11f5e217f5986098
Tx public key: 1ac4841e4c054554f07d6767074f8cfd44f9155ef2a89f2db01e970d9ca04334
| Timestamp: 1779453824 | Timestamp [UTC]: 2026-05-22 12:43:44 | Age [y:d:h:m:s]: 00:025:19:21:37 |
| Block: 357 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 8388 | RingCT/type: yes/0 |
| Extra: 011ac4841e4c054554f07d6767074f8cfd44f9155ef2a89f2db01e970d9ca0433402090000000393369e7d00 | ||
1 output(s) for total of 35.160489419861 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0bbdaca35f20d482829488e32fd56d7364042b4ed210812103a0a96cd9060011 | 35.160489419861 | 353 of 0 | <db> |
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": 417,
"vin": [ {
"gen": {
"height": 357
}
}
],
"vout": [ {
"amount": 35160489419861,
"target": {
"tagged_key": {
"key": "0bbdaca35f20d482829488e32fd56d7364042b4ed210812103a0a96cd9060011",
"view_tag": "db"
}
}
}
],
"extra": [ 1, 26, 196, 132, 30, 76, 5, 69, 84, 240, 125, 103, 103, 7, 79, 140, 253, 68, 249, 21, 94, 242, 168, 159, 45, 176, 30, 151, 13, 156, 160, 67, 52, 2, 9, 0, 0, 0, 3, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}