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: 6c327eaea3ed5a08728d1bac4e19727b7f77d2f4d065d863263d08561dc854b6
Tx prefix hash: cd0a881322bd81ebdd5a630d8133f62a48c0dae62d34d44d00a2ee10dae906d6
Tx public key: 27caafaeb79bf4925e4deb1e3b79fdd62c51303f578c7670d6f11ee3e4d07613
| Timestamp: 1780133587 | Timestamp [UTC]: 2026-05-30 09:33:07 | Age [y:d:h:m:s]: 00:009:13:45:46 |
| Block: 4954 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2932 | RingCT/type: yes/0 |
| Extra: 0127caafaeb79bf4925e4deb1e3b79fdd62c51303f578c7670d6f11ee3e4d0761302090000000226697be300 | ||
1 output(s) for total of 34.853546700397 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8d2b362c6640da5dd6fdb3333cf98bf420507a10c4355e16ae1074e9c3e2f4e7 | 34.853546700397 | 6297 of 0 | <74> |
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": 5014,
"vin": [ {
"gen": {
"height": 4954
}
}
],
"vout": [ {
"amount": 34853546700397,
"target": {
"tagged_key": {
"key": "8d2b362c6640da5dd6fdb3333cf98bf420507a10c4355e16ae1074e9c3e2f4e7",
"view_tag": "74"
}
}
}
],
"extra": [ 1, 39, 202, 175, 174, 183, 155, 244, 146, 94, 77, 235, 30, 59, 121, 253, 214, 44, 81, 48, 63, 87, 140, 118, 112, 214, 241, 30, 227, 228, 208, 118, 19, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}