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: 89f8972dd0ea08c09d31bf4e8f76322afb2112b4ce39529aefdab7fc3aaa2aa7
Tx prefix hash: f13381f63de70e4400189da81e535760e4f5a348a1dbdab6419154b4465f178a
Tx public key: 6e3cff3aec8b9ad8ad90b93bba10854ae012c986329cab60d3c284fc028df86b
| Timestamp: 1779980493 | Timestamp [UTC]: 2026-05-28 15:01:33 | Age [y:d:h:m:s]: 00:015:20:19:32 |
| Block: 3917 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4828 | RingCT/type: yes/0 |
| Extra: 016e3cff3aec8b9ad8ad90b93bba10854ae012c986329cab60d3c284fc028df86b02090000000126697be300 | ||
1 output(s) for total of 34.922552533376 HMNY
| stealth address | amount | amount idx | tag |
| 00: ad30a4f5beb7045c7331bfc06fcc75579f64073a6358a1700ba064c5d892216b | 34.922552533376 | 4811 of 0 | <29> |
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": 3977,
"vin": [ {
"gen": {
"height": 3917
}
}
],
"vout": [ {
"amount": 34922552533376,
"target": {
"tagged_key": {
"key": "ad30a4f5beb7045c7331bfc06fcc75579f64073a6358a1700ba064c5d892216b",
"view_tag": "29"
}
}
}
],
"extra": [ 1, 110, 60, 255, 58, 236, 139, 154, 216, 173, 144, 185, 59, 186, 16, 133, 74, 224, 18, 201, 134, 50, 156, 171, 96, 211, 194, 132, 252, 2, 141, 248, 107, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}