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: c07b7d4049811839803cef0522d1963028b91fffdacb1fea62d649ee46282491
Tx prefix hash: 871346119dda47880aee9f7306ff4d7b4ddea228910a76bd5342dfef5f3ec39f
Tx public key: 4b2ef584ede4f3c1b5920f2c33808958c3bba817dddebc9528d424257f433a0e
| Timestamp: 1780323046 | Timestamp [UTC]: 2026-06-01 14:10:46 | Age [y:d:h:m:s]: 00:007:11:25:11 |
| Block: 5046 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2840 | RingCT/type: yes/0 |
| Extra: 014b2ef584ede4f3c1b5920f2c33808958c3bba817dddebc9528d424257f433a0e02090000000d26697be300 | ||
1 output(s) for total of 34.847431267589 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0a98ddeb5f94177e2756ff141c4966dc1aa6b03afe595c43b0356e5bd1df7722 | 34.847431267589 | 6421 of 0 | <44> |
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": 5106,
"vin": [ {
"gen": {
"height": 5046
}
}
],
"vout": [ {
"amount": 34847431267589,
"target": {
"tagged_key": {
"key": "0a98ddeb5f94177e2756ff141c4966dc1aa6b03afe595c43b0356e5bd1df7722",
"view_tag": "44"
}
}
}
],
"extra": [ 1, 75, 46, 245, 132, 237, 228, 243, 193, 181, 146, 15, 44, 51, 128, 137, 88, 195, 187, 168, 23, 221, 222, 188, 149, 40, 212, 36, 37, 127, 67, 58, 14, 2, 9, 0, 0, 0, 13, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}