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: 033b15b2a722c52907441653b51bc843552ccb3779a31986c29bec974011ff53
Tx prefix hash: d26f1b341880669a40f09c41ef56335109c94c175b9e190275f88f5b4fbda18b
Tx public key: eda1bff8ed76d229735236177d684fc41d0c21f1657f34b21d919dda7cd26344
| Timestamp: 1779633571 | Timestamp [UTC]: 2026-05-24 14:39:31 | Age [y:d:h:m:s]: 00:015:10:07:16 |
| Block: 993 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6893 | RingCT/type: yes/0 |
| Extra: 01eda1bff8ed76d229735236177d684fc41d0c21f1657f34b21d919dda7cd26344020900000002ba6d17be00 | ||
1 output(s) for total of 35.117862972882 HMNY
| stealth address | amount | amount idx | tag |
| 00: 88a6fd07c34a0e41a3b9dc1554bc52584f103717e0b7c4bfbb69af699c04c2dd | 35.117862972882 | 1129 of 0 | <19> |
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": 1053,
"vin": [ {
"gen": {
"height": 993
}
}
],
"vout": [ {
"amount": 35117862972882,
"target": {
"tagged_key": {
"key": "88a6fd07c34a0e41a3b9dc1554bc52584f103717e0b7c4bfbb69af699c04c2dd",
"view_tag": "19"
}
}
}
],
"extra": [ 1, 237, 161, 191, 248, 237, 118, 210, 41, 115, 82, 54, 23, 125, 104, 79, 196, 29, 12, 33, 241, 101, 127, 52, 178, 29, 145, 157, 218, 124, 210, 99, 68, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}