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: 871607c0ea65015a15bacbbf8349f0f0d2c63f760216dbedd4727761154324d5
Tx prefix hash: 401d340d782665c426381b2d425c827490fe7a4ba72d5c243f266b8fdeabfbb5
Tx public key: 6970abb11fa8b85f3168b19264c304fd2c0b88fc6067f48ca385e1eb0a5f22e5
| Timestamp: 1779634073 | Timestamp [UTC]: 2026-05-24 14:47:53 | Age [y:d:h:m:s]: 00:015:10:48:04 |
| Block: 1017 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6869 | RingCT/type: yes/0 |
| Extra: 016970abb11fa8b85f3168b19264c304fd2c0b88fc6067f48ca385e1eb0a5f22e5020900000001ba6d17be00 | ||
1 output(s) for total of 35.116255439953 HMNY
| stealth address | amount | amount idx | tag |
| 00: d00312fc2ec49026c47204a2f52e9caf909061d3488078ad85251193f23e1a0a | 35.116255439953 | 1153 of 0 | <ec> |
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": 1077,
"vin": [ {
"gen": {
"height": 1017
}
}
],
"vout": [ {
"amount": 35116255439953,
"target": {
"tagged_key": {
"key": "d00312fc2ec49026c47204a2f52e9caf909061d3488078ad85251193f23e1a0a",
"view_tag": "ec"
}
}
}
],
"extra": [ 1, 105, 112, 171, 177, 31, 168, 184, 95, 49, 104, 177, 146, 100, 195, 4, 253, 44, 11, 136, 252, 96, 103, 244, 140, 163, 133, 225, 235, 10, 95, 34, 229, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}