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: fc18d6c9b9aa328a08914143e897b0a236118a4bb433760ee6998587e7d4360e
Tx prefix hash: 870c9ebaa9b7219f893c6955c10746901a87b4bd57241f0558ee9674b3e0545c
Tx public key: 395e7871d951bbbff8bf57440b887ed84d8a67dc4ec2660bc4a20c3a09aa669f
| Timestamp: 1780845948 | Timestamp [UTC]: 2026-06-07 15:25:48 | Age [y:d:h:m:s]: 00:001:09:20:59 |
| Block: 7505 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 381 | RingCT/type: yes/0 |
| Extra: 01395e7871d951bbbff8bf57440b887ed84d8a67dc4ec2660bc4a20c3a09aa669f020900000002e49593ff00 | ||
1 output(s) for total of 34.684373408808 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5bc2ef3958fa640d706789929effe1ad4689b49086119bb15d05b7a3e2d58c56 | 34.684373408808 | 9251 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": 7565,
"vin": [ {
"gen": {
"height": 7505
}
}
],
"vout": [ {
"amount": 34684373408808,
"target": {
"tagged_key": {
"key": "5bc2ef3958fa640d706789929effe1ad4689b49086119bb15d05b7a3e2d58c56",
"view_tag": "dd"
}
}
}
],
"extra": [ 1, 57, 94, 120, 113, 217, 81, 187, 191, 248, 191, 87, 68, 11, 136, 126, 216, 77, 138, 103, 220, 78, 194, 102, 11, 196, 162, 12, 58, 9, 170, 102, 159, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}