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: bad00697e3ca7d166358e038f346797138066e3654a636e2d9dee3253507147b
Tx prefix hash: 6b55e4f8e65e5e9b0cfb68e1b259f65c40b4b9522e9788b9ae309ec901f4501e
Tx public key: e32ab73ceb96c9815d562e69d6511b891dc664f5cf105a71377043a212746142
| Timestamp: 1780383934 | Timestamp [UTC]: 2026-06-02 07:05:34 | Age [y:d:h:m:s]: 00:006:18:30:23 |
| Block: 5166 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2720 | RingCT/type: yes/0 |
| Extra: 01e32ab73ceb96c9815d562e69d6511b891dc664f5cf105a71377043a21274614202090000000226697be300 | ||
1 output(s) for total of 34.839456228643 HMNY
| stealth address | amount | amount idx | tag |
| 00: bf1a2c0ddb8ddedbc53d92f57bd129ad7fadddd156da422ddb22ed620d753e61 | 34.839456228643 | 6545 of 0 | <f5> |
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": 5226,
"vin": [ {
"gen": {
"height": 5166
}
}
],
"vout": [ {
"amount": 34839456228643,
"target": {
"tagged_key": {
"key": "bf1a2c0ddb8ddedbc53d92f57bd129ad7fadddd156da422ddb22ed620d753e61",
"view_tag": "f5"
}
}
}
],
"extra": [ 1, 227, 42, 183, 60, 235, 150, 201, 129, 93, 86, 46, 105, 214, 81, 27, 137, 29, 198, 100, 245, 207, 16, 90, 113, 55, 112, 67, 162, 18, 116, 97, 66, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}