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: df93ea033d0252231ad29d4bcae1f9ce21e8d894346fe6949d903610d0f4362c
Tx prefix hash: beadb7187756cd6c7e9b4e51d30984ed91409d95ec8c564a20c73300ba2b10fd
Tx public key: a937b0dc1f1d73be0afc1322280978c719b5a3df60d36f3060ef99b52eab2b45
| Timestamp: 1779644522 | Timestamp [UTC]: 2026-05-24 17:42:02 | Age [y:d:h:m:s]: 00:015:07:53:55 |
| Block: 1434 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6452 | RingCT/type: yes/0 |
| Extra: 01a937b0dc1f1d73be0afc1322280978c719b5a3df60d36f3060ef99b52eab2b45020900000004ba6d17be00 | ||
1 output(s) for total of 35.088336299012 HMNY
| stealth address | amount | amount idx | tag |
| 00: fe8d56819b19baf9411a8d4ddfec74c16c3e0b48e2671a2594e28818e2ef08f4 | 35.088336299012 | 1588 of 0 | <67> |
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": 1494,
"vin": [ {
"gen": {
"height": 1434
}
}
],
"vout": [ {
"amount": 35088336299012,
"target": {
"tagged_key": {
"key": "fe8d56819b19baf9411a8d4ddfec74c16c3e0b48e2671a2594e28818e2ef08f4",
"view_tag": "67"
}
}
}
],
"extra": [ 1, 169, 55, 176, 220, 31, 29, 115, 190, 10, 252, 19, 34, 40, 9, 120, 199, 25, 181, 163, 223, 96, 211, 111, 48, 96, 239, 153, 181, 46, 171, 43, 69, 2, 9, 0, 0, 0, 4, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}