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: 5e6c7a54c37b4f0fd1ff850da6902197bd142cc8fda61410dca20772df8e308d
Tx prefix hash: f7f7179a88758f32c526605793a1655e4e43a8b116a376339b2c54aeaee9885a
Tx public key: 09a9b1e160293e258bfa83b8bdf4ca23b8586d0d4c49a5dbcda254ee7d2313b4
| Timestamp: 1779941038 | Timestamp [UTC]: 2026-05-28 04:03:58 | Age [y:d:h:m:s]: 00:011:23:34:52 |
| Block: 3496 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4446 | RingCT/type: yes/0 |
| Extra: 0109a9b1e160293e258bfa83b8bdf4ca23b8586d0d4c49a5dbcda254ee7d2313b402090000000226697be300 | ||
1 output(s) for total of 34.950606414439 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1f3326f289768a01373c07fcd37da5968cdbe2d5226802083f23b35187e2a537 | 34.950606414439 | 4215 of 0 | <89> |
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": 3556,
"vin": [ {
"gen": {
"height": 3496
}
}
],
"vout": [ {
"amount": 34950606414439,
"target": {
"tagged_key": {
"key": "1f3326f289768a01373c07fcd37da5968cdbe2d5226802083f23b35187e2a537",
"view_tag": "89"
}
}
}
],
"extra": [ 1, 9, 169, 177, 225, 96, 41, 62, 37, 139, 250, 131, 184, 189, 244, 202, 35, 184, 88, 109, 13, 76, 73, 165, 219, 205, 162, 84, 238, 125, 35, 19, 180, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}