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: db1ac4aec0ba333a5bae5de85999ad8c067214a50459e0adc62cdf921d6a2827
Tx prefix hash: 6343c1af4ee06f2c0a38a2ba9ef11ffb8e5d41c7fd2a4d6530b508cca74648dd
Tx public key: 3d3f2af8d75e0fe89f67871c63c25eb7a3fad962f3be03bff203d2e26a9a3e4b
| Timestamp: 1780841282 | Timestamp [UTC]: 2026-06-07 14:08:02 | Age [y:d:h:m:s]: 00:001:09:10:51 |
| Block: 7465 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 421 | RingCT/type: yes/0 |
| Extra: 013d3f2af8d75e0fe89f67871c63c25eb7a3fad962f3be03bff203d2e26a9a3e4b020900000001e49593ff00 | ||
1 output(s) for total of 34.687019719967 HMNY
| stealth address | amount | amount idx | tag |
| 00: a3c79cb91cb22afab311730f0643addf73be9c56a100019a59ddb6a027e6c59b | 34.687019719967 | 9195 of 0 | <d8> |
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": 7525,
"vin": [ {
"gen": {
"height": 7465
}
}
],
"vout": [ {
"amount": 34687019719967,
"target": {
"tagged_key": {
"key": "a3c79cb91cb22afab311730f0643addf73be9c56a100019a59ddb6a027e6c59b",
"view_tag": "d8"
}
}
}
],
"extra": [ 1, 61, 63, 42, 248, 215, 94, 15, 232, 159, 103, 135, 28, 99, 194, 94, 183, 163, 250, 217, 98, 243, 190, 3, 191, 242, 3, 210, 226, 106, 154, 62, 75, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}