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: c62107fa55d2047dd1c24dc9cef5506530b95e39a45c2844b514b98ecf782664
Tx prefix hash: 2d6c8834afea570c4a7f8c69071f52b22cc3b73f1d430a5410e2944963a76d52
Tx public key: b451a4936e0d666e15c0f37495d04a38f734278f79bdbbac371c6cb838110888
| Timestamp: 1780735148 | Timestamp [UTC]: 2026-06-06 08:39:08 | Age [y:d:h:m:s]: 00:002:16:56:49 |
| Block: 6358 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1528 | RingCT/type: yes/0 |
| Extra: 01b451a4936e0d666e15c0f37495d04a38f734278f79bdbbac371c6cb838110888020900000001e49593ff00 | ||
1 output(s) for total of 34.760336549788 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4bc7b19335e4d0cae57fb842ccb1cd8d31477a5678c9235459b1db22127c1e01 | 34.760336549788 | 7845 of 0 | <b2> |
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": 6418,
"vin": [ {
"gen": {
"height": 6358
}
}
],
"vout": [ {
"amount": 34760336549788,
"target": {
"tagged_key": {
"key": "4bc7b19335e4d0cae57fb842ccb1cd8d31477a5678c9235459b1db22127c1e01",
"view_tag": "b2"
}
}
}
],
"extra": [ 1, 180, 81, 164, 147, 110, 13, 102, 110, 21, 192, 243, 116, 149, 208, 74, 56, 247, 52, 39, 143, 121, 189, 187, 172, 55, 28, 108, 184, 56, 17, 8, 136, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}