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: ea0f7b5f449956e979c77d44ef713065558e1698a1b90e05c9e4abd39f22e0e8
Tx prefix hash: d67ac7eccb2d255a4e72f14b99956d1070d19f432d7702fd0b22e7f3a9205129
Tx public key: 2b44b9ae67be46680d8d55edeb530042e2c63b57c5f37ab08995c1002c8b382b
| Timestamp: 1780739706 | Timestamp [UTC]: 2026-06-06 09:55:06 | Age [y:d:h:m:s]: 00:002:15:40:51 |
| Block: 6398 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1488 | RingCT/type: yes/0 |
| Extra: 012b44b9ae67be46680d8d55edeb530042e2c63b57c5f37ab08995c1002c8b382b020900000001e49593ff00 | ||
1 output(s) for total of 34.757684645207 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5e8e4f274b1e88d49c26ff7ec9b7317e950f27c963f204d73f4bdf7c939141be | 34.757684645207 | 7889 of 0 | <32> |
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": 6458,
"vin": [ {
"gen": {
"height": 6398
}
}
],
"vout": [ {
"amount": 34757684645207,
"target": {
"tagged_key": {
"key": "5e8e4f274b1e88d49c26ff7ec9b7317e950f27c963f204d73f4bdf7c939141be",
"view_tag": "32"
}
}
}
],
"extra": [ 1, 43, 68, 185, 174, 103, 190, 70, 104, 13, 141, 85, 237, 235, 83, 0, 66, 226, 198, 59, 87, 197, 243, 122, 176, 137, 149, 193, 0, 44, 139, 56, 43, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}