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: bc5bae40f3d789f6f33b23dd70cec817dfa7350cc9aabfb02034a7e0dd484905
Tx prefix hash: e4a8da9716e2d0d649f5fd9c7cc15ad0ed9310db45fd16fde9e010c529fdcfce
Tx public key: 8185ee109392089fb3270574ddfba64150a98c8bf9a875e49319c911f5ddb16e
| Timestamp: 1780849480 | Timestamp [UTC]: 2026-06-07 16:24:40 | Age [y:d:h:m:s]: 00:001:06:00:09 |
| Block: 7535 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 351 | RingCT/type: yes/0 |
| Extra: 018185ee109392089fb3270574ddfba64150a98c8bf9a875e49319c911f5ddb16e020900000001e49593ff00 | ||
1 output(s) for total of 34.682388807930 HMNY
| stealth address | amount | amount idx | tag |
| 00: bdf3813d5dd71de89e1ee7ac43148e27fd955d18c98129e2886f25d7192a22fe | 34.682388807930 | 9293 of 0 | <53> |
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": 7595,
"vin": [ {
"gen": {
"height": 7535
}
}
],
"vout": [ {
"amount": 34682388807930,
"target": {
"tagged_key": {
"key": "bdf3813d5dd71de89e1ee7ac43148e27fd955d18c98129e2886f25d7192a22fe",
"view_tag": "53"
}
}
}
],
"extra": [ 1, 129, 133, 238, 16, 147, 146, 8, 159, 179, 39, 5, 116, 221, 251, 166, 65, 80, 169, 140, 139, 249, 168, 117, 228, 147, 25, 201, 17, 245, 221, 177, 110, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}