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: 53a1c19ebbf924ec8e0c56b96e26f2145cdef1b2637815e21e001291ded8bf72
Tx prefix hash: ab14d969e776d18ced0514f42ab40199b2d0ba96ce9b63d20bc44d43526b6dda
Tx public key: f1b780f0143e653aeae02af2d17dfc08f7a58e09b5a6ba24efcefbeb3ab11ee2
| Timestamp: 1779936722 | Timestamp [UTC]: 2026-05-28 02:52:02 | Age [y:d:h:m:s]: 00:011:23:48:34 |
| Block: 3446 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4450 | RingCT/type: yes/0 |
| Extra: 01f1b780f0143e653aeae02af2d17dfc08f7a58e09b5a6ba24efcefbeb3ab11ee202090000000626697be300 | ||
1 output(s) for total of 34.953939726128 HMNY
| stealth address | amount | amount idx | tag |
| 00: 49c03051c2468adc2d4f448866a3fded2207bacfb882b56a8d06a7a69f4300e9 | 34.953939726128 | 4163 of 0 | <08> |
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": 3506,
"vin": [ {
"gen": {
"height": 3446
}
}
],
"vout": [ {
"amount": 34953939726128,
"target": {
"tagged_key": {
"key": "49c03051c2468adc2d4f448866a3fded2207bacfb882b56a8d06a7a69f4300e9",
"view_tag": "08"
}
}
}
],
"extra": [ 1, 241, 183, 128, 240, 20, 62, 101, 58, 234, 224, 42, 242, 209, 125, 252, 8, 247, 165, 142, 9, 181, 166, 186, 36, 239, 206, 251, 235, 58, 177, 30, 226, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}