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: 17d4ebab13a1e87e2ea942165017dc4b164efc9d8d4830c3b202dea6cb274708
Tx prefix hash: ca500c6c7d92b5242143e19d62cc665205d220b5f7bcdf43c64ea4dc5db2d4fa
Tx public key: 275045b7a555bccad7b0729dcf6025fbe2a0fdd01f0dca00a61f515e62b33b16
| Timestamp: 1780698382 | Timestamp [UTC]: 2026-06-05 22:26:22 | Age [y:d:h:m:s]: 00:003:03:09:35 |
| Block: 6023 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1863 | RingCT/type: yes/0 |
| Extra: 01275045b7a555bccad7b0729dcf6025fbe2a0fdd01f0dca00a61f515e62b33b16020900000001e49593ff00 | ||
1 output(s) for total of 34.782554195266 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6dd8d86dc3c43214ae14db3f45149f37ec737058ec6fd29d5cf618355fe81b4a | 34.782554195266 | 7490 of 0 | <88> |
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": 6083,
"vin": [ {
"gen": {
"height": 6023
}
}
],
"vout": [ {
"amount": 34782554195266,
"target": {
"tagged_key": {
"key": "6dd8d86dc3c43214ae14db3f45149f37ec737058ec6fd29d5cf618355fe81b4a",
"view_tag": "88"
}
}
}
],
"extra": [ 1, 39, 80, 69, 183, 165, 85, 188, 202, 215, 176, 114, 157, 207, 96, 37, 251, 226, 160, 253, 208, 31, 13, 202, 0, 166, 31, 81, 94, 98, 179, 59, 22, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}