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: 8eafb98f9348ba50de74ecb2a1c5eda63f2ff374894b713a8cd40b8c8385b778
Tx prefix hash: 178cc70239265e5b1c1246910432deddc09fd6fd772c3485dbc7cdc946bb205c
Tx public key: 8ace6d2392f9bf57c60b0feedefcc88d85291f63cac3eba6a87c78ca38f992e6
| Timestamp: 1780394357 | Timestamp [UTC]: 2026-06-02 09:59:17 | Age [y:d:h:m:s]: 00:006:16:41:19 |
| Block: 5239 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2657 | RingCT/type: yes/0 |
| Extra: 018ace6d2392f9bf57c60b0feedefcc88d85291f63cac3eba6a87c78ca38f992e602090000000226697be300 | ||
1 output(s) for total of 34.834605639502 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9daa77d7947463924d22d41e3900ef3ff56017b9da1a2e91d9b92f3fa72a9b60 | 34.834605639502 | 6632 of 0 | <47> |
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": 5299,
"vin": [ {
"gen": {
"height": 5239
}
}
],
"vout": [ {
"amount": 34834605639502,
"target": {
"tagged_key": {
"key": "9daa77d7947463924d22d41e3900ef3ff56017b9da1a2e91d9b92f3fa72a9b60",
"view_tag": "47"
}
}
}
],
"extra": [ 1, 138, 206, 109, 35, 146, 249, 191, 87, 198, 11, 15, 238, 222, 252, 200, 141, 133, 41, 31, 99, 202, 195, 235, 166, 168, 124, 120, 202, 56, 249, 146, 230, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}