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: a3aa24289db0cd040cef56ae3af35eaaa0e4c8c99695704d7ee673852229f183
Tx prefix hash: 1e21af70185e95cc35e032466f77faeb24a55728779a473f8c81b7c48f78c2e1
Tx public key: 5c9e36e3da5c821ca06ee9fea6c0b6f62df14fdc341652465d4ee3d8d6e59e2f
| Timestamp: 1779643405 | Timestamp [UTC]: 2026-05-24 17:23:25 | Age [y:d:h:m:s]: 00:015:08:12:32 |
| Block: 1413 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6473 | RingCT/type: yes/0 |
| Extra: 015c9e36e3da5c821ca06ee9fea6c0b6f62df14fdc341652465d4ee3d8d6e59e2f020900000002ba6d17be00 | ||
1 output(s) for total of 35.089741767996 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4d7abd8f67489bc585a334a32066460f3db3a4b35476c537a74bf6fa43b6cd93 | 35.089741767996 | 1565 of 0 | <16> |
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": 1473,
"vin": [ {
"gen": {
"height": 1413
}
}
],
"vout": [ {
"amount": 35089741767996,
"target": {
"tagged_key": {
"key": "4d7abd8f67489bc585a334a32066460f3db3a4b35476c537a74bf6fa43b6cd93",
"view_tag": "16"
}
}
}
],
"extra": [ 1, 92, 158, 54, 227, 218, 92, 130, 28, 160, 110, 233, 254, 166, 192, 182, 246, 45, 241, 79, 220, 52, 22, 82, 70, 93, 78, 227, 216, 214, 229, 158, 47, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}