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: 45935aed22eb79b8d38587e9d950752e5aa48a86436987061da239ce8a437c74
Tx prefix hash: ec6ebe921fb451afef5dffff50ed184076b8e2d508c3e3a107b356b5bec05c06
Tx public key: 0db65a3979ab74957cde151cc1171d6bb15bd741a9e1afdb9f8e8d391b3e37f3
| Timestamp: 1780825166 | Timestamp [UTC]: 2026-06-07 09:39:26 | Age [y:d:h:m:s]: 00:001:17:59:24 |
| Block: 7244 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 698 | RingCT/type: yes/0 |
| Extra: 010db65a3979ab74957cde151cc1171d6bb15bd741a9e1afdb9f8e8d391b3e37f3020900000001e49593ff00 | ||
1 output(s) for total of 34.709063828949 HMNY
| stealth address | amount | amount idx | tag |
| 00: 542c4bc48ac3615754d14e6cd3dda59f6bb84662515aa92011a979ad84e91c45 | 34.709063828949 | 8920 of 0 | <66> |
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": 7304,
"vin": [ {
"gen": {
"height": 7244
}
}
],
"vout": [ {
"amount": 34709063828949,
"target": {
"tagged_key": {
"key": "542c4bc48ac3615754d14e6cd3dda59f6bb84662515aa92011a979ad84e91c45",
"view_tag": "66"
}
}
}
],
"extra": [ 1, 13, 182, 90, 57, 121, 171, 116, 149, 124, 222, 21, 28, 193, 23, 29, 107, 177, 91, 215, 65, 169, 225, 175, 219, 159, 142, 141, 57, 27, 62, 55, 243, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}