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: 5ccb89f00709ec668f76e786cd7d4894a5c0d8faf9e0c14bfe7c1be6e77fe18c
Tx prefix hash: 8508abd5f2a52e0bdd10d7f42ff4ee132c2f52ff921a7a4f9bf80322408951be
Tx public key: 80337d04653562ebc30e75496a46ed691747cb3712b9b8e2ef282d7d6c7dbee4
| Timestamp: 1780688673 | Timestamp [UTC]: 2026-06-05 19:44:33 | Age [y:d:h:m:s]: 00:011:12:44:39 |
| Block: 5542 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3203 | RingCT/type: yes/0 |
| Extra: 0180337d04653562ebc30e75496a46ed691747cb3712b9b8e2ef282d7d6c7dbee4020900000001e49593ff00 | ||
1 output(s) for total of 34.814479590114 HMNY
| stealth address | amount | amount idx | tag |
| 00: c5ff3d0d9d12efa14fc061490f9321c8ebb9b2d7475344001bd0169eefd2c77d | 34.814479590114 | 6985 of 0 | <31> |
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": 5602,
"vin": [ {
"gen": {
"height": 5542
}
}
],
"vout": [ {
"amount": 34814479590114,
"target": {
"tagged_key": {
"key": "c5ff3d0d9d12efa14fc061490f9321c8ebb9b2d7475344001bd0169eefd2c77d",
"view_tag": "31"
}
}
}
],
"extra": [ 1, 128, 51, 125, 4, 101, 53, 98, 235, 195, 14, 117, 73, 106, 70, 237, 105, 23, 71, 203, 55, 18, 185, 184, 226, 239, 40, 45, 125, 108, 125, 190, 228, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}