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: bfa86db9159492627289ba78538ab06e888e04e48cb0a05e100acdd85e42dbe5
Tx prefix hash: 566c20005a1562bf33a0025d433ba91f15e00626a4816cd08e34d212205b7d29
Tx public key: 93edfebab36cc72dfb5b56a018e56d95f5e7e36e4578fbca37a10089493b2d2f
| Timestamp: 1780848748 | Timestamp [UTC]: 2026-06-07 16:12:28 | Age [y:d:h:m:s]: 00:001:07:06:25 |
| Block: 7529 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 357 | RingCT/type: yes/0 |
| Extra: 0193edfebab36cc72dfb5b56a018e56d95f5e7e36e4578fbca37a10089493b2d2f020900000004e49593ff00 | ||
1 output(s) for total of 34.682785719021 HMNY
| stealth address | amount | amount idx | tag |
| 00: af9dd22564a08803489191c21e2affdcbde10f2b576fe04f54fa01b2fd2b045c | 34.682785719021 | 9285 of 0 | <45> |
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": 7589,
"vin": [ {
"gen": {
"height": 7529
}
}
],
"vout": [ {
"amount": 34682785719021,
"target": {
"tagged_key": {
"key": "af9dd22564a08803489191c21e2affdcbde10f2b576fe04f54fa01b2fd2b045c",
"view_tag": "45"
}
}
}
],
"extra": [ 1, 147, 237, 254, 186, 179, 108, 199, 45, 251, 91, 86, 160, 24, 229, 109, 149, 245, 231, 227, 110, 69, 120, 251, 202, 55, 161, 0, 137, 73, 59, 45, 47, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}