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: 0c5ce2a975dc8dfc82caa83376e6f337140a223b060630d86b5f89223cd912fc
Tx prefix hash: 2bd71451c18ed7fce74c206c4185fc40db76c93ce5315bb57bb08080141a1c87
Tx public key: c3a802f73181f8b04a577a56133305305276006305795d621d9e1fe72b3ef740
| Timestamp: 1779450492 | Timestamp [UTC]: 2026-05-22 11:48:12 | Age [y:d:h:m:s]: 00:017:14:52:24 |
| Block: 318 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7579 | RingCT/type: yes/0 |
| Extra: 01c3a802f73181f8b04a577a56133305305276006305795d621d9e1fe72b3ef7400209000000034438f87f00 | ||
1 output(s) for total of 35.163104988781 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0c65d20fc94e378b20c64cf659c4474a2c1f7c2867a645b736434de8d9085327 | 35.163104988781 | 314 of 0 | <fd> |
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": 378,
"vin": [ {
"gen": {
"height": 318
}
}
],
"vout": [ {
"amount": 35163104988781,
"target": {
"tagged_key": {
"key": "0c65d20fc94e378b20c64cf659c4474a2c1f7c2867a645b736434de8d9085327",
"view_tag": "fd"
}
}
}
],
"extra": [ 1, 195, 168, 2, 247, 49, 129, 248, 176, 74, 87, 122, 86, 19, 51, 5, 48, 82, 118, 0, 99, 5, 121, 93, 98, 29, 158, 31, 231, 43, 62, 247, 64, 2, 9, 0, 0, 0, 3, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}