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: d66444d23ab9985610360fa087c4e0f83217d679e2446c4b55e5f4962300bd0a
Tx prefix hash: 8fa7423d83ed91774ecb77b366ecfe1976cdc6fa655419aae7fccb1ac9127313
Tx public key: 1e17ad5156edadd0bccadc71680d1f3ef4a3797484fc40a8b90d18fdc458c558
| Timestamp: 1779844473 | Timestamp [UTC]: 2026-05-27 01:14:33 | Age [y:d:h:m:s]: 00:012:22:04:20 |
| Block: 2434 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5452 | RingCT/type: yes/0 |
| Extra: 011e17ad5156edadd0bccadc71680d1f3ef4a3797484fc40a8b90d18fdc458c55802090000000226697be300 | ||
1 output(s) for total of 35.021474329793 HMNY
| stealth address | amount | amount idx | tag |
| 00: 790a1b30a758419b1f973559e420d07f035a1844f1ca5158f73689b5dc1e887b | 35.021474329793 | 2860 of 0 | <d5> |
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": 2494,
"vin": [ {
"gen": {
"height": 2434
}
}
],
"vout": [ {
"amount": 35021474329793,
"target": {
"tagged_key": {
"key": "790a1b30a758419b1f973559e420d07f035a1844f1ca5158f73689b5dc1e887b",
"view_tag": "d5"
}
}
}
],
"extra": [ 1, 30, 23, 173, 81, 86, 237, 173, 208, 188, 202, 220, 113, 104, 13, 31, 62, 244, 163, 121, 116, 132, 252, 64, 168, 185, 13, 24, 253, 196, 88, 197, 88, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}