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: 20bd41bc636643a33e5ae5334efdb6ec8014a3761635d9f78380e3b9cf28fe8f
Tx prefix hash: 745cf7c34cd7871e0704bd12262267e3f88e11e46428ac1f437e5baf342d4941
Tx public key: 0e3ce2817962df597c6892b88faab35b57c4a0a20138d4917e0ce0f0c4009fb5
| Timestamp: 1781010229 | Timestamp [UTC]: 2026-06-09 13:03:49 | Age [y:d:h:m:s]: 00:006:03:39:25 |
| Block: 8581 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 164 | RingCT/type: yes/0 |
| Extra: 010e3ce2817962df597c6892b88faab35b57c4a0a20138d4917e0ce0f0c4009fb502090000001be49593ff00 | ||
1 output(s) for total of 34.618292548984 HMNY
| stealth address | amount | amount idx | tag |
| 00: a03e6301cec6d9f0de3593602a413bc8f034aff338dd6eb2b82941e3e5206877 | 34.618292548984 | 10601 of 0 | <4a> |
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": 8641,
"vin": [ {
"gen": {
"height": 8581
}
}
],
"vout": [ {
"amount": 34618292548984,
"target": {
"tagged_key": {
"key": "a03e6301cec6d9f0de3593602a413bc8f034aff338dd6eb2b82941e3e5206877",
"view_tag": "4a"
}
}
}
],
"extra": [ 1, 14, 60, 226, 129, 121, 98, 223, 89, 124, 104, 146, 184, 143, 170, 179, 91, 87, 196, 160, 162, 1, 56, 212, 145, 126, 12, 224, 240, 196, 0, 159, 181, 2, 9, 0, 0, 0, 27, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}