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: 61f667b318fa1753ab9154dba3f3b2482d0654cb19fbc68e628b1765b281b554
Tx prefix hash: 935020492b03fadb617bc6fd3e2cbaa93f8ded1cbab37c54580e694fba18fd0f
Tx public key: 499bd1f2788d3b9b513374eea7680c3183235674e5fd879aa9b6ff70140f75db
| Timestamp: 1779882624 | Timestamp [UTC]: 2026-05-27 11:50:24 | Age [y:d:h:m:s]: 00:012:13:45:33 |
| Block: 2966 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4920 | RingCT/type: yes/0 |
| Extra: 01499bd1f2788d3b9b513374eea7680c3183235674e5fd879aa9b6ff70140f75db02090000000126697be300 | ||
1 output(s) for total of 34.998159697765 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4df5da89b0bba6651e1bc7afc1ccda3900c6dc53b7781ac3df8868582404861f | 34.998159697765 | 3518 of 0 | <64> |
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": 3026,
"vin": [ {
"gen": {
"height": 2966
}
}
],
"vout": [ {
"amount": 34998159697765,
"target": {
"tagged_key": {
"key": "4df5da89b0bba6651e1bc7afc1ccda3900c6dc53b7781ac3df8868582404861f",
"view_tag": "64"
}
}
}
],
"extra": [ 1, 73, 155, 209, 242, 120, 141, 59, 155, 81, 51, 116, 238, 167, 104, 12, 49, 131, 35, 86, 116, 229, 253, 135, 154, 169, 182, 255, 112, 20, 15, 117, 219, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}