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: 0c73e5706a455dc535af8017b93d0aa16da8538a4ddd8aa297524d0c8c7c9621
Tx prefix hash: bdaa2f428a5e724b676cef6b539e402fdd02116d3e5baa12c315d60a73389f1d
Tx public key: 912fc7571d1e2410630e6a29040d375a418d6e6930df9c414069a3aaab6b8065
| Timestamp: 1780805810 | Timestamp [UTC]: 2026-06-07 04:16:50 | Age [y:d:h:m:s]: 00:001:21:19:07 |
| Block: 6943 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 943 | RingCT/type: yes/0 |
| Extra: 01912fc7571d1e2410630e6a29040d375a418d6e6930df9c414069a3aaab6b8065020900000001e49593ff00 | ||
1 output(s) for total of 34.721572596200 HMNY
| stealth address | amount | amount idx | tag |
| 00: 749b20b2b09aac10552634cc26a9713c4abe45bb3f22c031e66c85a3d59d87ff | 34.721572596200 | 8563 of 0 | <eb> |
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": 7003,
"vin": [ {
"gen": {
"height": 6943
}
}
],
"vout": [ {
"amount": 34721572596200,
"target": {
"tagged_key": {
"key": "749b20b2b09aac10552634cc26a9713c4abe45bb3f22c031e66c85a3d59d87ff",
"view_tag": "eb"
}
}
}
],
"extra": [ 1, 145, 47, 199, 87, 29, 30, 36, 16, 99, 14, 106, 41, 4, 13, 55, 90, 65, 141, 110, 105, 48, 223, 156, 65, 64, 105, 163, 170, 171, 107, 128, 101, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}