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: 189f33ac2f1971ddc0634022a6990f70a93906135ddaaffdf48cc90d37244af5
Tx prefix hash: 482d71fe59b3771b07093d05d39a2f6a2e5fc1b254c689579a738c85bb752de0
Tx public key: 4f01cd5932d9bc24d8f7fb6b0b9a4fa547abf639655695d1df580a2d3ca4fad5
| Timestamp: 1779461220 | Timestamp [UTC]: 2026-05-22 14:47:00 | Age [y:d:h:m:s]: 00:017:10:48:57 |
| Block: 441 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7445 | RingCT/type: yes/0 |
| Extra: 014f01cd5932d9bc24d8f7fb6b0b9a4fa547abf639655695d1df580a2d3ca4fad502090000000293369e7d00 | ||
1 output(s) for total of 35.154856547583 HMNY
| stealth address | amount | amount idx | tag |
| 00: f9db8457b0b1143af4436ab112ee06aa702cf21ddf7e725cb08d0b8bec81dd23 | 35.154856547583 | 445 of 0 | <dd> |
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": 501,
"vin": [ {
"gen": {
"height": 441
}
}
],
"vout": [ {
"amount": 35154856547583,
"target": {
"tagged_key": {
"key": "f9db8457b0b1143af4436ab112ee06aa702cf21ddf7e725cb08d0b8bec81dd23",
"view_tag": "dd"
}
}
}
],
"extra": [ 1, 79, 1, 205, 89, 50, 217, 188, 36, 216, 247, 251, 107, 11, 154, 79, 165, 71, 171, 246, 57, 101, 86, 149, 209, 223, 88, 10, 45, 60, 164, 250, 213, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}