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: 15ce72d65d1c95f0d9294f54c5af2ec3f6249680f843913f2c64d1ab6fbeafb4
Tx prefix hash: 18b6926d4017a3ded40db2299523f8bf83ee5a6b6f50c3e0ca8da14b79dc8cdb
Tx public key: 296fcf60ddb288a8034bbd169bd5a5c7cc70bc6f36c413f3d2910e33c60f4d8d
| Timestamp: 1781014813 | Timestamp [UTC]: 2026-06-09 14:20:13 | Age [y:d:h:m:s]: 00:006:01:53:40 |
| Block: 8622 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 123 | RingCT/type: yes/0 |
| Extra: 01296fcf60ddb288a8034bbd169bd5a5c7cc70bc6f36c413f3d2910e33c60f4d8d020900000001e49593ff00 | ||
1 output(s) for total of 34.615569050257 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7de0e8410eeb86e37491eb873d9538d85758ab2892709e15a35b232dc03d858e | 34.615569050257 | 10656 of 0 | <a2> |
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": 8682,
"vin": [ {
"gen": {
"height": 8622
}
}
],
"vout": [ {
"amount": 34615569050257,
"target": {
"tagged_key": {
"key": "7de0e8410eeb86e37491eb873d9538d85758ab2892709e15a35b232dc03d858e",
"view_tag": "a2"
}
}
}
],
"extra": [ 1, 41, 111, 207, 96, 221, 178, 136, 168, 3, 75, 189, 22, 155, 213, 165, 199, 204, 112, 188, 111, 54, 196, 19, 243, 210, 145, 14, 51, 198, 15, 77, 141, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}