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: 5bdf2853f0b309a4814c1982e6104fa5616cf89bafd8f5ca766730437278c4d6
Tx prefix hash: 3e7655581982f23cae176fc7519e0ba8f2ce3ec5fd41f739d93d802f34b02fbb
Tx public key: 024b27236b8f789217b279508fb1a00f6fa307647a215cf6fcf17ab37584b87c
| Timestamp: 1779465888 | Timestamp [UTC]: 2026-05-22 16:04:48 | Age [y:d:h:m:s]: 00:017:10:45:00 |
| Block: 509 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7391 | RingCT/type: yes/0 |
| Extra: 01024b27236b8f789217b279508fb1a00f6fa307647a215cf6fcf17ab37584b87c02090000000493369e7d00 | ||
1 output(s) for total of 35.150297264316 HMNY
| stealth address | amount | amount idx | tag |
| 00: 487541570bf18b2f434f02ebb7f5736fabc395ad588a3050193181968aa8f07a | 35.150297264316 | 513 of 0 | <1b> |
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": 569,
"vin": [ {
"gen": {
"height": 509
}
}
],
"vout": [ {
"amount": 35150297264316,
"target": {
"tagged_key": {
"key": "487541570bf18b2f434f02ebb7f5736fabc395ad588a3050193181968aa8f07a",
"view_tag": "1b"
}
}
}
],
"extra": [ 1, 2, 75, 39, 35, 107, 143, 120, 146, 23, 178, 121, 80, 143, 177, 160, 15, 111, 163, 7, 100, 122, 33, 92, 246, 252, 241, 122, 179, 117, 132, 184, 124, 2, 9, 0, 0, 0, 4, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}