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: ad1831f5a9e0c917db92b3961a905596fea5477231cd166acd7dc74719f3c3fc
Tx prefix hash: 2fb414842283041a998bc60d35d643f0e34136d39db816813511c5c001957c87
Tx public key: 71f22380cae039d19d926c36874793ef75bfa2e4e835583405b6754557c231ca
| Timestamp: 1779475309 | Timestamp [UTC]: 2026-05-22 18:41:49 | Age [y:d:h:m:s]: 00:017:06:54:08 |
| Block: 606 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7280 | RingCT/type: yes/0 |
| Extra: 0171f22380cae039d19d926c36874793ef75bfa2e4e835583405b6754557c231ca02090000000293369e7d00 | ||
1 output(s) for total of 35.143794604142 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9850bf12b83cd7b711c981a69da5a9a2a7bccdded9375e1bf4613b551938d61c | 35.143794604142 | 624 of 0 | <bf> |
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": 666,
"vin": [ {
"gen": {
"height": 606
}
}
],
"vout": [ {
"amount": 35143794604142,
"target": {
"tagged_key": {
"key": "9850bf12b83cd7b711c981a69da5a9a2a7bccdded9375e1bf4613b551938d61c",
"view_tag": "bf"
}
}
}
],
"extra": [ 1, 113, 242, 35, 128, 202, 224, 57, 209, 157, 146, 108, 54, 135, 71, 147, 239, 117, 191, 162, 228, 232, 53, 88, 52, 5, 182, 117, 69, 87, 194, 49, 202, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}