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: be6ab4580c5203235a7af98378850c6895798f491b905fe47092c655196b852c
Tx prefix hash: a23c2c22782b9d5e088dc492140302d853c1877fc58f61b105114fc6fea631e4
Tx public key: 554026cb01b88da9dfcc18ffd619e6984d993b051784cbe86c0b62d74a7d02ad
| Timestamp: 1781022477 | Timestamp [UTC]: 2026-06-09 16:27:57 | Age [y:d:h:m:s]: 00:006:05:09:27 |
| Block: 8708 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 37 | RingCT/type: yes/0 |
| Extra: 01554026cb01b88da9dfcc18ffd619e6984d993b051784cbe86c0b62d74a7d02ad020900000001e49593ff00 | ||
1 output(s) for total of 34.604879872222 HMNY
| stealth address | amount | amount idx | tag |
| 00: f3afa1db7b2f1ebafe29a6fa1712347cdf704b65d60770f8edb8f97f334595f2 | 34.604879872222 | 10768 of 0 | <da> |
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": 8768,
"vin": [ {
"gen": {
"height": 8708
}
}
],
"vout": [ {
"amount": 34604879872222,
"target": {
"tagged_key": {
"key": "f3afa1db7b2f1ebafe29a6fa1712347cdf704b65d60770f8edb8f97f334595f2",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 85, 64, 38, 203, 1, 184, 141, 169, 223, 204, 24, 255, 214, 25, 230, 152, 77, 153, 59, 5, 23, 132, 203, 232, 108, 11, 98, 215, 74, 125, 2, 173, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}