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: 2943f453c289e5070f37d2df509042ab5f67e5d1dc4087e263b610d27fe9f21a
Tx prefix hash: ba0fdf0eda263c3dad96f3d52c261a7dea7ed676c8191a8adab5903c1b2165ae
Tx public key: fc962c37198405e67c1b1eae5680558718350597eba9155d1e7ee7bf376f103c
| Timestamp: 1779970054 | Timestamp [UTC]: 2026-05-28 12:07:34 | Age [y:d:h:m:s]: 00:011:16:25:28 |
| Block: 3839 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4191 | RingCT/type: yes/0 |
| Extra: 01fc962c37198405e67c1b1eae5680558718350597eba9155d1e7ee7bf376f103c02090000000526697be300 | ||
1 output(s) for total of 34.927748464490 HMNY
| stealth address | amount | amount idx | tag |
| 00: f68205fa9b9a546d78cea04e6d409b5329fca67ce4ace43e449967020b03237e | 34.927748464490 | 4682 of 0 | <a2> |
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": 3899,
"vin": [ {
"gen": {
"height": 3839
}
}
],
"vout": [ {
"amount": 34927748464490,
"target": {
"tagged_key": {
"key": "f68205fa9b9a546d78cea04e6d409b5329fca67ce4ace43e449967020b03237e",
"view_tag": "a2"
}
}
}
],
"extra": [ 1, 252, 150, 44, 55, 25, 132, 5, 230, 124, 27, 30, 174, 86, 128, 85, 135, 24, 53, 5, 151, 235, 169, 21, 93, 30, 126, 231, 191, 55, 111, 16, 60, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}