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: 0f90d72be1b7a59bd37eff999bf447f20e0d08038ae19a1ca2e1644fd38ed2b2
Tx prefix hash: f938d16eec732a3013020bf7c894f2e782a5e86a9b4a7ff0d93a05a1b7b5fbdd
Tx public key: 376d07cb0b7d57e3578e4e93bdf86766b5d062fa269bad3a312fc4c47f3c0c0f
| Timestamp: 1780693423 | Timestamp [UTC]: 2026-06-05 21:03:43 | Age [y:d:h:m:s]: 00:003:20:05:20 |
| Block: 5870 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2864 | RingCT/type: yes/0 |
| Extra: 01376d07cb0b7d57e3578e4e93bdf86766b5d062fa269bad3a312fc4c47f3c0c0f020900000001e49593ff00 | ||
1 output(s) for total of 34.792706082109 HMNY
| stealth address | amount | amount idx | tag |
| 00: cb6f28aff649a5b7a5ab77f182f8b15742a730ebf7c782f0cc8065fdd1cee65e | 34.792706082109 | 7329 of 0 | <c3> |
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": 5930,
"vin": [ {
"gen": {
"height": 5870
}
}
],
"vout": [ {
"amount": 34792706082109,
"target": {
"tagged_key": {
"key": "cb6f28aff649a5b7a5ab77f182f8b15742a730ebf7c782f0cc8065fdd1cee65e",
"view_tag": "c3"
}
}
}
],
"extra": [ 1, 55, 109, 7, 203, 11, 125, 87, 227, 87, 142, 78, 147, 189, 248, 103, 102, 181, 208, 98, 250, 38, 155, 173, 58, 49, 47, 196, 196, 127, 60, 12, 15, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}