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: 1096948cf00c2dba9a9fa57882da19e834d5ed5ac927e47af3c4e67d6e9ae9b0
Tx prefix hash: 1d350c9533cbbd375b6daee4c0187ee670c526c78a57139177e71da844201d46
Tx public key: a9ca9b0bc1fb45f732ed746b7684ded3e21c3c55d46f45d25a985e5c06442370
| Timestamp: 1780690729 | Timestamp [UTC]: 2026-06-05 20:18:49 | Age [y:d:h:m:s]: 00:003:07:32:09 |
| Block: 5679 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2308 | RingCT/type: yes/0 |
| Extra: 01a9ca9b0bc1fb45f732ed746b7684ded3e21c3c55d46f45d25a985e5c06442370020900000001e49593ff00 | ||
1 output(s) for total of 34.805383510968 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7f5bd319c4942f0e5f7a0a64601c89f1fd89323b60e5a4c1c8a02a9a5373642b | 34.805383510968 | 7128 of 0 | <53> |
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": 5739,
"vin": [ {
"gen": {
"height": 5679
}
}
],
"vout": [ {
"amount": 34805383510968,
"target": {
"tagged_key": {
"key": "7f5bd319c4942f0e5f7a0a64601c89f1fd89323b60e5a4c1c8a02a9a5373642b",
"view_tag": "53"
}
}
}
],
"extra": [ 1, 169, 202, 155, 11, 193, 251, 69, 247, 50, 237, 116, 107, 118, 132, 222, 211, 226, 28, 60, 85, 212, 111, 69, 210, 90, 152, 94, 92, 6, 68, 35, 112, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}