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: 73c63078669e70ea924e867d0feb42b062cfebbdfb622ceb8faf8d7bacb0b78d
Tx prefix hash: cdae29ceb054217eb0daacd1c9953be9c42ec70e3bdd8ee08b2efc1a3769f59d
Tx public key: 27b7a8e4593cc2eec1ad042abffc384fb82bc12d13b4de0b6f4a51f54a6e171a
| Timestamp: 1780741884 | Timestamp [UTC]: 2026-06-06 10:31:24 | Age [y:d:h:m:s]: 00:003:06:37:39 |
| Block: 6416 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2318 | RingCT/type: yes/0 |
| Extra: 0127b7a8e4593cc2eec1ad042abffc384fb82bc12d13b4de0b6f4a51f54a6e171a020900000002e49593ff00 | ||
1 output(s) for total of 34.756491354152 HMNY
| stealth address | amount | amount idx | tag |
| 00: dea932586061ce245eceeddb79d857b05068c0096dfcc7312b554b3f2a194043 | 34.756491354152 | 7907 of 0 | <ee> |
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": 6476,
"vin": [ {
"gen": {
"height": 6416
}
}
],
"vout": [ {
"amount": 34756491354152,
"target": {
"tagged_key": {
"key": "dea932586061ce245eceeddb79d857b05068c0096dfcc7312b554b3f2a194043",
"view_tag": "ee"
}
}
}
],
"extra": [ 1, 39, 183, 168, 228, 89, 60, 194, 238, 193, 173, 4, 42, 191, 252, 56, 79, 184, 43, 193, 45, 19, 180, 222, 11, 111, 74, 81, 245, 74, 110, 23, 26, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}