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: e8b3aa4a166972e30a6c082b80821e64944a9137e02065727408b1e87df9d1f4
Tx prefix hash: 59d15054cfa802a88900ef15822da69d7d6976e942868ea9c76c7fc3a3cb9cb2
Tx public key: 626d6ca65e513c6e68dc459753f97541b750361935b91ddb8b4f094a7bda0d40
| Timestamp: 1780707335 | Timestamp [UTC]: 2026-06-06 00:55:35 | Age [y:d:h:m:s]: 00:003:01:45:01 |
| Block: 6127 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1770 | RingCT/type: yes/0 |
| Extra: 01626d6ca65e513c6e68dc459753f97541b750361935b91ddb8b4f094a7bda0d40020900000003e49593ff00 | ||
1 output(s) for total of 34.775655257413 HMNY
| stealth address | amount | amount idx | tag |
| 00: e46d3cfdcfd5f601ce07841c576dd7dcddfd1b729fb699665362acd21ef27612 | 34.775655257413 | 7600 of 0 | <31> |
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": 6187,
"vin": [ {
"gen": {
"height": 6127
}
}
],
"vout": [ {
"amount": 34775655257413,
"target": {
"tagged_key": {
"key": "e46d3cfdcfd5f601ce07841c576dd7dcddfd1b729fb699665362acd21ef27612",
"view_tag": "31"
}
}
}
],
"extra": [ 1, 98, 109, 108, 166, 94, 81, 60, 110, 104, 220, 69, 151, 83, 249, 117, 65, 183, 80, 54, 25, 53, 185, 29, 219, 139, 79, 9, 74, 123, 218, 13, 64, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}