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: 48b77c7d51dd3810f24be1fd67cf94e5bd977d524e89f796d82e0fab2704cf26
Tx prefix hash: 04a1e189367c40b9a6f98b6541e28a07c970c1e116e6a491f72873fcf2f90e67
Tx public key: 7db8c6f4e92c128f79d441ec5c9aba97de05f626325064b2a117f1c81d297d6c
| Timestamp: 1780706224 | Timestamp [UTC]: 2026-06-06 00:37:04 | Age [y:d:h:m:s]: 00:003:03:01:46 |
| Block: 6113 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1833 | RingCT/type: yes/0 |
| Extra: 017db8c6f4e92c128f79d441ec5c9aba97de05f626325064b2a117f1c81d297d6c020900000001e49593ff00 | ||
1 output(s) for total of 34.776583880876 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7d3a776b5e97fd81851a2205cf1acfb03dada848d7301cf441794a7259396489 | 34.776583880876 | 7586 of 0 | <97> |
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": 6173,
"vin": [ {
"gen": {
"height": 6113
}
}
],
"vout": [ {
"amount": 34776583880876,
"target": {
"tagged_key": {
"key": "7d3a776b5e97fd81851a2205cf1acfb03dada848d7301cf441794a7259396489",
"view_tag": "97"
}
}
}
],
"extra": [ 1, 125, 184, 198, 244, 233, 44, 18, 143, 121, 212, 65, 236, 92, 154, 186, 151, 222, 5, 246, 38, 50, 80, 100, 178, 161, 23, 241, 200, 29, 41, 125, 108, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}