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: ba06f3aab4b0fb515252fb8037d6e41e767dd6a003b4092a8d07a4cea3288f08
Tx prefix hash: aefd6ce6a02bdee916018127de3dc96c924a36d47576a0fcdbadc890d07ecd2c
Tx public key: f389c46f9492c628faa3a6e8e9e765c963faf240be22c46f3a5e802e530c3a1c
| Timestamp: 1779955146 | Timestamp [UTC]: 2026-05-28 07:59:06 | Age [y:d:h:m:s]: 00:011:16:47:41 |
| Block: 3678 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4208 | RingCT/type: yes/0 |
| Extra: 01f389c46f9492c628faa3a6e8e9e765c963faf240be22c46f3a5e802e530c3a1c02090000000426697be300 | ||
1 output(s) for total of 34.944199844053 HMNY
| stealth address | amount | amount idx | tag |
| 00: b47132eda58c198e4d7e394cbc1b95e2df17d69c9f953917e238903f5b7ec161 | 34.944199844053 | 4445 of 0 | <3a> |
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": 3738,
"vin": [ {
"gen": {
"height": 3678
}
}
],
"vout": [ {
"amount": 34944199844053,
"target": {
"tagged_key": {
"key": "b47132eda58c198e4d7e394cbc1b95e2df17d69c9f953917e238903f5b7ec161",
"view_tag": "3a"
}
}
}
],
"extra": [ 1, 243, 137, 196, 111, 148, 146, 198, 40, 250, 163, 166, 232, 233, 231, 101, 201, 99, 250, 242, 64, 190, 34, 196, 111, 58, 94, 128, 46, 83, 12, 58, 28, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}