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: 4eb47fac8a49d52369ac096474c2f7c9c343c6ed654dcb72aca8cc63f2e88311
Tx prefix hash: 211f19937b956b9baac7f324fb6fa6508495bfa46764c5af2e4eab798676a348
Tx public key: 9133bd5e8a600c07820f437111fe09f9d99997297c1a73324cf5cff1dc503927
| Timestamp: 1780322804 | Timestamp [UTC]: 2026-06-01 14:06:44 | Age [y:d:h:m:s]: 00:007:11:29:13 |
| Block: 5019 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2867 | RingCT/type: yes/0 |
| Extra: 019133bd5e8a600c07820f437111fe09f9d99997297c1a73324cf5cff1dc50392702090000000426697be300 | ||
1 output(s) for total of 34.849225902921 HMNY
| stealth address | amount | amount idx | tag |
| 00: d5f1d519add58e6aae8b2bbcec1f6558880c43c882f21122e6ea4a1ebfa1ac92 | 34.849225902921 | 6392 of 0 | <9f> |
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": 5079,
"vin": [ {
"gen": {
"height": 5019
}
}
],
"vout": [ {
"amount": 34849225902921,
"target": {
"tagged_key": {
"key": "d5f1d519add58e6aae8b2bbcec1f6558880c43c882f21122e6ea4a1ebfa1ac92",
"view_tag": "9f"
}
}
}
],
"extra": [ 1, 145, 51, 189, 94, 138, 96, 12, 7, 130, 15, 67, 113, 17, 254, 9, 249, 217, 153, 151, 41, 124, 26, 115, 50, 76, 245, 207, 241, 220, 80, 57, 39, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}