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: 390529e25d420cdf801a30ba9df824e39e6a528769a7cd37a4c786958a864443
Tx prefix hash: 31fe2540e9f22c5350359f024546332a43e214c98fd544f3d7b6cf68b6925218
Tx public key: 6c64fdf6f2fd8f72cf2e10e6e3653f32d3ccea4e23aad2dfbe860dc589b50cae
| Timestamp: 1780853497 | Timestamp [UTC]: 2026-06-07 17:31:37 | Age [y:d:h:m:s]: 00:001:05:47:16 |
| Block: 7555 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 331 | RingCT/type: yes/0 |
| Extra: 016c64fdf6f2fd8f72cf2e10e6e3653f32d3ccea4e23aad2dfbe860dc589b50cae020900000006e49593ff00 | ||
1 output(s) for total of 34.686089003765 HMNY
| stealth address | amount | amount idx | tag |
| 00: 32fadca7788dedd7cbfcdee70d4c5603f87a173bf41a549297327293d424db4f | 34.686089003765 | 9325 of 0 | <3b> |
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": 7615,
"vin": [ {
"gen": {
"height": 7555
}
}
],
"vout": [ {
"amount": 34686089003765,
"target": {
"tagged_key": {
"key": "32fadca7788dedd7cbfcdee70d4c5603f87a173bf41a549297327293d424db4f",
"view_tag": "3b"
}
}
}
],
"extra": [ 1, 108, 100, 253, 246, 242, 253, 143, 114, 207, 46, 16, 230, 227, 101, 63, 50, 211, 204, 234, 78, 35, 170, 210, 223, 190, 134, 13, 197, 137, 181, 12, 174, 2, 9, 0, 0, 0, 6, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}