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: 602c4b12eeee448fef9be3798409331ed8fe037c5872ddb366bb6e4acb598eab
Tx prefix hash: b660aaa43c6ef2e8a9ba410723190f8152248cecd3d58a8344e472a9e4df388d
Tx public key: 418cac2b3bd7c942b361b8a9b5c7c9c04d24c5264a398b0db1bf2ebf686e5dc0
| Timestamp: 1779956487 | Timestamp [UTC]: 2026-05-28 08:21:27 | Age [y:d:h:m:s]: 00:011:17:14:30 |
| Block: 3698 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4188 | RingCT/type: yes/0 |
| Extra: 01418cac2b3bd7c942b361b8a9b5c7c9c04d24c5264a398b0db1bf2ebf686e5dc002090000000226697be300 | ||
1 output(s) for total of 34.937143071120 HMNY
| stealth address | amount | amount idx | tag |
| 00: a64e793ace24319a87559cf9bfa327f33230b843eea3a2367bf73f9501ab1f9f | 34.937143071120 | 4474 of 0 | <fa> |
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": 3758,
"vin": [ {
"gen": {
"height": 3698
}
}
],
"vout": [ {
"amount": 34937143071120,
"target": {
"tagged_key": {
"key": "a64e793ace24319a87559cf9bfa327f33230b843eea3a2367bf73f9501ab1f9f",
"view_tag": "fa"
}
}
}
],
"extra": [ 1, 65, 140, 172, 43, 59, 215, 201, 66, 179, 97, 184, 169, 181, 199, 201, 192, 77, 36, 197, 38, 74, 57, 139, 13, 177, 191, 46, 191, 104, 110, 93, 192, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}