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: 4d190824378baddc8da2d2acb65abf7dd3ab4d7f0692a9ee6257b60fa472af60
Tx prefix hash: 90a84810c732516e392d5084ed46fb038f30ffdde98fb426b7b24b3fd62e258b
Tx public key: caffab9e996d48084141396369a0b66deb34d6357b3a7c997e659b3a1c6b38dd
| Timestamp: 1780831909 | Timestamp [UTC]: 2026-06-07 11:31:49 | Age [y:d:h:m:s]: 00:005:23:30:27 |
| Block: 7353 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1392 | RingCT/type: yes/0 |
| Extra: 01caffab9e996d48084141396369a0b66deb34d6357b3a7c997e659b3a1c6b38dd020900000001e49593ff00 | ||
1 output(s) for total of 34.694430465399 HMNY
| stealth address | amount | amount idx | tag |
| 00: 65e19cc06edbfbb0043a555f0f27fc919c100f7e8066a4512f60eb8c850835d8 | 34.694430465399 | 9053 of 0 | <8d> |
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": 7413,
"vin": [ {
"gen": {
"height": 7353
}
}
],
"vout": [ {
"amount": 34694430465399,
"target": {
"tagged_key": {
"key": "65e19cc06edbfbb0043a555f0f27fc919c100f7e8066a4512f60eb8c850835d8",
"view_tag": "8d"
}
}
}
],
"extra": [ 1, 202, 255, 171, 158, 153, 109, 72, 8, 65, 65, 57, 99, 105, 160, 182, 109, 235, 52, 214, 53, 123, 58, 124, 153, 126, 101, 155, 58, 28, 107, 56, 221, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}