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: c494bb84f39bab21cb067bc93488d3a23ce6b42c6d0d868097fcf521543bf87c
Tx prefix hash: 0ebf26407ba5277389dc5923a1ad24091b96eec4267e8cdcf9fdf5593b3ffeba
Tx public key: c6d73e48a136e80d2a54757f2f373b021f9c88bbc6152c8d4ad9871d1cf7a8a1
| Timestamp: 1780049443 | Timestamp [UTC]: 2026-05-29 10:10:43 | Age [y:d:h:m:s]: 00:010:14:36:04 |
| Block: 4377 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3509 | RingCT/type: yes/0 |
| Extra: 01c6d73e48a136e80d2a54757f2f373b021f9c88bbc6152c8d4ad9871d1cf7a8a102090000000226697be300 | ||
1 output(s) for total of 34.896139979775 HMNY
| stealth address | amount | amount idx | tag |
| 00: e6910958b1877c3f2ee9c59790d22a4c6a31a16d3340b65d58dc0ab25a3bc082 | 34.896139979775 | 5474 of 0 | <01> |
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": 4437,
"vin": [ {
"gen": {
"height": 4377
}
}
],
"vout": [ {
"amount": 34896139979775,
"target": {
"tagged_key": {
"key": "e6910958b1877c3f2ee9c59790d22a4c6a31a16d3340b65d58dc0ab25a3bc082",
"view_tag": "01"
}
}
}
],
"extra": [ 1, 198, 215, 62, 72, 161, 54, 232, 13, 42, 84, 117, 127, 47, 55, 59, 2, 31, 156, 136, 187, 198, 21, 44, 141, 74, 217, 135, 29, 28, 247, 168, 161, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}