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: 012ff41518ab773835da0c7cdc96d1166c692169bf36b278a8c3c9f24a998a58
Tx prefix hash: 29e4951c6e601096db3fc8115f0c3e85ddee85b9dccdadfd782f7a4db59226ab
Tx public key: 5e2d2a0fc6cb8f1ee87067e447e37203463fd40732cbf3c84978f1c237c12e11
| Timestamp: 1779909384 | Timestamp [UTC]: 2026-05-27 19:16:24 | Age [y:d:h:m:s]: 00:012:07:33:24 |
| Block: 3226 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4674 | RingCT/type: yes/0 |
| Extra: 015e2d2a0fc6cb8f1ee87067e447e37203463fd40732cbf3c84978f1c237c12e1102090000000126697be300 | ||
1 output(s) for total of 34.968610074678 HMNY
| stealth address | amount | amount idx | tag |
| 00: 724489b12ac1e5b4cd76d9c0e067963e4c63fb744238abef24a6699aa8c55667 | 34.968610074678 | 3868 of 0 | <da> |
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": 3286,
"vin": [ {
"gen": {
"height": 3226
}
}
],
"vout": [ {
"amount": 34968610074678,
"target": {
"tagged_key": {
"key": "724489b12ac1e5b4cd76d9c0e067963e4c63fb744238abef24a6699aa8c55667",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 94, 45, 42, 15, 198, 203, 143, 30, 232, 112, 103, 228, 71, 227, 114, 3, 70, 63, 212, 7, 50, 203, 243, 200, 73, 120, 241, 194, 55, 193, 46, 17, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}