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: 9256247509ef9aca705b44a14eadcd9737f2b48a6d4f0dd3f1f18f1ea13a255b
Tx prefix hash: d2b1dbb77ac0abdc17225b7743780a9294e32f492da632e4562788efb115255d
Tx public key: 743486afc7bedc8404335509ef2db64fdefac7b514aa20380b00d14e6c6e0e33
| Timestamp: 1779766580 | Timestamp [UTC]: 2026-05-26 03:36:20 | Age [y:d:h:m:s]: 00:014:00:02:30 |
| Block: 1973 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5969 | RingCT/type: yes/0 |
| Extra: 01743486afc7bedc8404335509ef2db64fdefac7b514aa20380b00d14e6c6e0e3302090000000126697be300 | ||
1 output(s) for total of 35.052281853832 HMNY
| stealth address | amount | amount idx | tag |
| 00: 854acd6a85f9eab216ca924b1929ef2be91f9cfaf34ce8b7fbf88b779d5cb593 | 35.052281853832 | 2243 of 0 | <46> |
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": 2033,
"vin": [ {
"gen": {
"height": 1973
}
}
],
"vout": [ {
"amount": 35052281853832,
"target": {
"tagged_key": {
"key": "854acd6a85f9eab216ca924b1929ef2be91f9cfaf34ce8b7fbf88b779d5cb593",
"view_tag": "46"
}
}
}
],
"extra": [ 1, 116, 52, 134, 175, 199, 190, 220, 132, 4, 51, 85, 9, 239, 45, 182, 79, 222, 250, 199, 181, 20, 170, 32, 56, 11, 0, 209, 78, 108, 110, 14, 51, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}